问题
Using a WinCE C# Forms app .NET3.5 on device link
I can deploy fine and run the forms application.
I can use the Windows CE Test Kit link which automatically deploys itself to the device and it runs the tests.
Problem: Debugging wont start. It locks up VS2008. It seems to deploy the app fine, then hangs. Eventually comes up with "Unable to start debugging"
I cannot use SOTI link as it fails to deploy itself to the device
回答1:
The fact that CETK works is a red herring. It uses a different transport (PlatMan) so whether or not is works actually has no bearing of whether a managed app will work (which uses CoreCon).
Studio debugging is very solid provided you have the right and same versions of CoreCon on the desktop and the device. Have you upgraded to the latest service pack of Studio? Does the target have CoreCon on it already? Is the target version of CoreCon the same as what's on the development PC? Do you have CF 3.5 only on the target, or is 2.0 also installed? Is it the same SP version of the CF as you have on the PC?
回答2:
i already resolved this trouble by steps 1. Open MS Vs 2005->VS remote tool->remote registry editor Highlight Windows CE 5.0 -> HKLM -> System Right click in the right hand pane and select New DWORD value. In the name field type (exactly and without the quotes) "CoreConOverrideSecurity" and set its value to 1 Close the editor. Shut down the emulator with Save State. refer: http://wincetips.blogspot.com/
回答3:
I were getting "unable to start" popup after the successful deployment in the emulator. The CE Remote Process viewer tool could not show the trace of my program being added in the emulator. I have tried to attach the process of emulator to the VS2008 but it failed. Later I have reinstalled full installation of VS2008. It fixed the problem.
来源：https://stackoverflow.com/questions/4220830/wince-unable-to-start-debugging