Automation Interfaces
A version of this page is also available for
4/8/2010
The following table shows the Automation 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 returns error information for applications that return rich error information. |
|
This interface provides the tools for creating and administering the type information defined through the type description. |
|
This interface derives from ICreateTypeInfo and adds methods for deleting items that have been added through ICreateTypeInfo. |
|
This interface provides the methods for creating and managing the component or file that contains type information. |
|
ICreateTypeLib2 inherits from ICreateTypeLib, and has four member functions. |
|
This interface exposes objects, methods, and properties to Automation programming tools and other applications. |
|
This interface provides a method for enumerating a collection of variants, including heterogeneous collections of objects and intrinsic types. |
|
This interface provides detailed contextual error information for applications that receive rich information. |
|
This interface ensures that error information can be propagated up the call chain correctly. |
|
This interface provides a fast way to access information that compilers need when binding to and instantiating structures and interfaces. |
|
This interface is typically used for reading information about objects. |
|
This interface allows ITypeInfo to cast to an ITypeInfo2 in performance-sensitive cases. |
|
This interface provides methods for accessing a library of type descriptions. |
|
This interface inherits from the ITypeLib interface. |