UPnP in Windows Mobile Devices
4/8/2010
The implementation of UPnP available for Windows Mobile devices is similar but not identical to the implementation available to OEMs that build platforms using Windows Embedded CE and Platform Builder.
Note
The UPnP documentation has been updated to reflect Windows Mobile device differences. However, in cases where the other UPnP documentation differs from the information in this topic, the information in this topic takes precedence.
The following list outlines important notes relevant when considering UPnP for use with Windows Mobile devices:
- UPnP for use on Windows Mobile devices ships in multiple CAB files (and supporting include and library files) that each contain some UPnP functionality. OEMs or application developers can include these CAB files in a new or existing installation, or install them manually, to add UPnP functionality to a Windows Mobile device. For detailed information about the CAB and other files available to OEMs and application developers, see Optional Server Components.
- UPnP for use on Windows Mobile devices does not include the C language API available to Windows Embedded CE OEMs. Instead, use the COM-based API. For more information about the COM-based control point and device APIs, see UPnP Application Development and UPnP Reference.
- The UPnP AV Framework only supports building control points on Windows Mobile devices. You cannot use the UPnP AV Framework to build a UPnP AV MediaRenderer or MediaServer device.
- By default on Windows Mobile devices, UPnP listens on no network interfaces. It does this by defining the ExcludeAllExceptListed registry setting. To enable UPnP, you must use the Interfaces registry setting to specify the network interfaces used by UPnP. For more information about these registry settings, see UPnP Registry Settings.