See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The following table shows the OLE interfaces with a description of the purpose of each.
 Note: |
|---|
| Windows Mobile may not support all of the programming elements in this section. For information about differences between the COM implementation available for Windows Mobile devices and that available for Windows Embedded CE devices, see COM and DCOM in Windows Mobile Devices. |
| Programming element | Description |
|---|---|
|
This interface enables containers and other objects to receive notifications of data, view, and compound-document changes occurring in objects of interest. |
|
|
This interface enumerates the different verbs available for an object in order of ascending verb number. |
|
|
This interface manages advisory connections and compound document notifications in an object server. |
|
|
This interface is the primary means by which an embedded object obtains information about the location and extent of its display site, moniker, user interface, and other resources provided by its container. |
|
|
This interface is used to enumerate objects in a compound document or lock a container in the running state. |
|
|
This interface manages interaction between the container and the object's in-place client site. |
|
|
This interface is the principal means by which an embedded object provides basic functionality to and communicates with its container. |
|
|
This interface provides methods that allow an application to obtain the handle to the various windows that participate in in-place activation, and also to enter and exit context-sensitive help mode. |
|
|
This interface enables an object to display itself directly without passing a data object to the caller. |