Troubleshooting Plug-in Development (Windows Embedded CE 6.0)
1/6/2010
You can avoid encountering common mistakes and errors during the development process for plug-ins based on the Microsoft Remote Tools Framework. This topic provides information about how to avoid encountering failure to load, deployment, and certification installation issues during plug-in development and testing.
Device-side Component Fails to Load
If deployment of the device-side component fails, the cause might be that the target device is not specified, or it is not linked to the correct libraries.
For Pocket PC for Windows Mobile 2003 and Smartphone for Windows Mobile 2003 devices, make sure that you specify the ARMV4 library. For devices based on other versions of Windows Mobile, specify the ARMV4I library.
Certification Errors
To run the plug-ins on actual devices, you might need to install certificates associated with those devices. The emulators in Windows Embedded CE 6.0 are provisioned to run certification tests.
Build Errors Due to SDKs That Are Not Installed
If your developer workstation does not have the software development kits (SDKs) for Windows Mobile Version 5.0 installed, you will encounter error messages during the build process. The following example shows the error messages that you encounter if you do not have the SDKs for Windows Mobile Version 5.0 installed.
Building .CETool Remote Tool Bundle for {PluginDescription}...
Adding component Component {OutputBundleName} C:\Program Files\Microsoft Remote Tools Framework\Samples\{OutputBundleName} ... DesktopSide\bin\Debug\{DesktopComponentName}.dll...
RemoteToolBundler : error : RemoteToolBundler : error : in line 50 ofC:\Program Files\Microsoft Remote Tools Framework\Samples\{OutputBundleName}\\plugininfo.cebundleinfo: The file C:\Program Files\Microsoft Remote Tools Framework\Samples\{OutputBundleName}\DeviceSideARMV4I\Windows Mobile 5.0 Smartphone SDK (ARMV4I)\Debug\DeviceComponent.exe does not exist, and will not be added to the bundle.
This occurs because the bundler could not find the device-side component for ARMV4I, which is installed with the SDK for Windows Mobile Version 5.0. To resolve this issue, install the SDK for Windows Mobile Version 5.0 and then run the build again.