Interface Key (Windows Embedded CE 6.0)

1/6/2010

This key registers new interfaces by associating an interface name with an interface ID (IID). The named values are stored under the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface

If your application adds a new interface, the Interface key must be completed for OLE 2 to register the new interface. There must be one IID subkey for each new interface.

Note

You must use ProxyStubCLSID32 because the IID-to-CLSID mapping may be different for 16-and 32-bit interfaces. The IID-to-CLSID depends on the way the interface proxies are packaged into a set of proxy DLLs.

The following table shows the named values for the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface key.

Value : type	Description
\<IID> = name of interface	Provides the textual name for a given interface. For example: \{00000112-0000-0000-C000-0000000000-46} = IOleObject If your application adds a new interface, the interface key must be completed for OLE 2 to register the new interface. There must be one entry for each new interface.
\BaseInterface = <name of interface>	Identifies the interface from which the current interface is derived.
\NumMethods = <number of methods>	Contains the number of interfaces in the associated interface.
\ProxyStubClsid32 = <CLSID>	Maps an IID to a CLSID in 32-bit proxy DLLs. This is a required entry because the IID-to-CLSID mapping may be different for 16- and 32-bit interfaces. The IID-to-CLSID mapping depends on the way the interface proxies are packaged into a set of proxy DLLs. If you add interfaces, you must use this entry to register them (32-bit systems) so that OLE can find the appropriate remoting code to establish interprocess communication.

See Also

Concepts

COM and DCOM Registry Settings
COM and DCOM Security

Other Resources

Component Services (COM and DCOM)
Enhancing the Security of a Device