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. |
After you have implemented the functionality of your MediaRenderer or MediaServer device by creating derived classes, as described in Implementing Device Classes, the remaining step is to expose these classes so that they can be used by the Device Host API.
The UPnP AV Framework plugs into and relies on the Device Host API for much of its functionality, including making service implementations available on the network.
This requires implementing an IUPnPDeviceControlCOM object and registering it with the Device Host API. Windows Mobile provides objects that implement IUPnPDeviceControlby deferring service object creation and implementations to UPnP AV Framework C++ classes you create. For more information about UPnP registration, see Implementing a Hosted Device Using COMand Registering a Hosted Device.
While the IConnectionManagerImplclass provides a significant amount of connection and protocol management functionality, you still need to provide the protocol information that your device supports. To do this, use IConnectionManagerImpl::AddSourceProtocoland IConnectionManagerImpl::AddSinkProtocol.
In addition to registering the IUPnPDeviceControl instance with the Device Host API, the appropriate UPnP XML device and service description documents must be located in the \Windows\UPnP directory on the device. Starting points for these documents are available on the UPnP web site, referenced in UPnP AV DCP Documentation.