Signing Device-Side Binaries before Distributing Plug-ins (Windows Embedded CE 6.0)
1/6/2010
If you are targeting a Remote Tools Framework plug-in, consider having your device side binaries authenticated. You can have your device-side binaries authenticated by code signing them, which can be done as a post-build event in the device-side project in your plug-in solution. If your device-side binaries are not authenticated properly, they may not run on a Windows Embedded CE powered device.
To have your plug-in code signed
Obtain the publisher certificate from an M2M Certificate Authority.
Modify your device-side project settings to include a post-build event to run Signtool to sign your device-side binaries with the certificate that you obtained in Step 1.
Build the plug-in with Release configuration as usual, letting the .cetool file build completely.
Upload the publisher-signed, device-side binaries from your build folders to the Certificate Authority.
The Certificate Authority will sign your plug-in with a Mobile2Market certificate and return it to you.
Put the device-side binaries signed by the Certificate Authority into the same location that they were before Step 4.
Do one of the following:
Delete the built .cetool file, and build your solution to rebundle your .cetool file.
Important
Do not rebuild or clean the solution, or you will delete the signed device-side binaries.
- or -