When a Windows CE device is connected through ActiveSync, deploymentand debugging (F5 and Ctrl-F5) fail with the typical error message”There were deployment errors. Continue?
Cause: Due tothe fact that ActiveSync 3.5 and 3.6 do not provide accurateinformation about the device instruction set, ConMan (Visual Studio.NET 2003 component for device connectivity) cannot use the informationreturned by ActiveSync to map a Windows CE device to the right .NETCompact Framework target (MIPSII, ARMV4 etc). Workaround:Install and run the separately provided Windows CE ConfigurationAdd-In. For ARMV4 devices, an alternative is to select Pocket PC Deviceat the beginning of the deployment. 11.2. 为什么不能通过ActiveSync调试 CEPC 或其他 x86 的Windows CE设备？ Symptom:After running the Windows CE Device Configuration Add-In, the user candeploy without debugging (Ctrl-F5) to an ActiveSync connected CEPC (orany x86 based Windows CE device) but cannot debug (F5). Non-x86 basedWindows CE devices do not have this problem. Cause:Debugging Windows CE Emulators (also x86 based) uses a TCP port thatconflicts with the one used by ActiveSync for debugging x86 baseddevices. To support Emulator debugging,
Related Questions
- When a Windows CE device is connected through ActiveSync, deploymentand debugging (F5 and Ctrl-F5) fail with the typical error message"There were deployment errors. Continue?
- How does an ActiveSync provider know whether it is dealing with a connected or a selected Windows CE-based device?
- Can I use the CowCalf5 Palm software on a Windows CE device?
