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. |
A version of this page is also available for
4/8/2010
There are two ways desktop applications can be notified that connection has been made with a Windows Embedded CE–based device:
- In
registry-based notification, connection and disconnection
are predefined events, each with its own registry key. Each key can
be assigned a command line to be executed when the corresponding
event occurs.
- In
COM-based notification, two interfaces—
IDccMan(provided by Rapi.dll) and
IDccManSink(implemented by the application seeking
notification) — handle connection/disconnection and related
actions.
The fundamental difference between registry- and COM-based notification is that registry-based notification simply causes a program to run. COM-based notification provides programmatic connection with those applications that want to be notified. This makes possible control of the connection manager, registering and deregistering for connection notification, or any kind of operation best-handled from within the application that creates the data to be synchronized.