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

This interface is used by desktop applications to find connected Windows Embedded CE–based remote devices in order to make Remote API 2 method calls. Applications will create an instance of this interface by calling COM's CoCreateInstanceExmethod. Once the instance has been obtained, the EnumDevicesand FindDevicemethods of the interface can be used to obtain a reference to a IRAPIDeviceinterface that represents a connected device.

The Adviseand UnAdvisemethods allow desktop applications to be registered with the connection manager and be alerted when devices connect and disconnect. To use this functionality, applications must implement the IRAPISinkinterface.

Methods

The following table shows the methods for this interface in alphabetical order. Like all COM interfaces, this interface inherits the methods for the IUnknowninterface.

Method Description

Advise

Registers an IRAPISink object to receive connection events.

EnumDevices

Returns an IRAPIEnumDevices object that can be used to enumerate connected remote devices.

FindDevice

Returns an IRAPIDevice object representing a connected remote device.

UnAdvise

Removes the registration of an IRAPISink object so that it will no longer receive connection events.

Requirements

Header rapi2.h
Library ole32.lib, rapiuuid.lib
Windows Embedded CE Windows Embedded CE 6.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.