Tools for Development

This section describes the various certificates and keys, libraries, and SDKs you will need to program using the Windows Media Device Manager SDK.

Certificates and Keys

The Windows Media Device Manager SDK ships with a test key/certificate pair (in the key.c file) that can be used by an application or a service provider to use Windows Media Device Manager methods on unprotected content. This key/certificate pair allows the application or service provider to use most of the Windows Media Device Manager functionality.

However, to develop an application or service provider that can handle DRM-protected content, you must request one or more certificates (each with a key) from the Windows Media Licensing Page. Certificates are required for the following applications or objects:

• Service Providers that handle DRM-protected content require a Windows Media Device Manager Service Provider Certificate (and key)
• Applications that transfer DRM-protected content require a Windows Media Device Manager Transfer Certificate (and key)
• Applications that play DRM-protected content require a DRM Certificate (and key).
• License metering components require a metering certificate. This is provided by a license metering service built on the Windows Media Rights Manager SDK, which can be requested on the Windows Media Licensing Page.

Libraries and Headers

In addition to the libraries and headers mentioned in Required Library and Header Files for an Application or Required Libraries and Headers for a Service Provider, any application or plug-in that formerly linked to WMDRMSDK.lib to call Windows Media Format SDK functions should now instead link to WMDRMSDKStub.Lib. This library file is used to access DRM-protected files. You can request this library from the Windows Media Licensing Page as well.

Related SDKs

The following Microsoft SDKs provide elements you may need in designing solutions for portable media devices.

See Also

• Getting Started