Debugging WinCE platform with Visual Studio 2008

[rnhunt]

Hi,

I have previously been using Embedded Visual C++ tools on a custom WinCE5
platform, with all the latest updates.

I now need to move to a .net based framework. I have added in .net from the
catalog and also ensured SYSGEN_WCELOAD is also added. The resultant image I
can connect to fine using ActiveSync over USB (explore files etc.) and the
Embedded Visual C++ remote tools and debug also runs fine.

However, Visual Studio 2008 struggles to connect to the device. It may
succeed on the third attempt after a couple of minutes.

If lucky, it may also decide to let me deploy files.

If I do get past the above hurdles, it won’t then let me run or debug the
files. It just hangs and eventually gives up.

I have built an emulator version (ARMV4I, version 3) and Visual Studio
connects and deploys to this fine. However, it also suffers from the same
run/debug problem except this time it gives me an immediate error message
“The remote computer does not have CLR version which is compatible ...”.

If I physically copy the files to the device using ActiveSync and run this
then the program runs in the .net framework as expected.

I have tried adding in other components, new platforms, CoreCon, and both
CF2 and CF3.5. No difference.

So, two questions I’m seeking advice on:

1. Why does it take an eternity to connect and deploy to a real device with
Visual Studio, if it succeeds at all?

2. Why won’t let me Visual Studio debug a program – what WinCE components
am I missing? I can run a program using CTRL-F5.

I have read some of the information in this thread and can confirm edm2.exe
is running as a process when I hit this problem.

Thanks in advance for any help.

[Paul G. Tobey [eMVP]]

DO NOT build both 2.0 and 3.5 into the device. This does not work at all.

If your application uses .NET CF 3.5 and .NET CF 2.0 is on the device, VS
will attempt to deploy the 3.5 version, since that's what your application
is built for, before deploying the application itself. There's an option
for this in the project settings for a .NET CF-based application.

Paul T.

Post by rnhunt
Hi,
I have previously been using Embedded Visual C++ tools on a custom WinCE5
platform, with all the latest updates.
I now need to move to a .net based framework. I have added in .net from the
catalog and also ensured SYSGEN_WCELOAD is also added. The resultant image I
can connect to fine using ActiveSync over USB (explore files etc.) and the
Embedded Visual C++ remote tools and debug also runs fine.
However, Visual Studio 2008 struggles to connect to the device. It may
succeed on the third attempt after a couple of minutes.
If lucky, it may also decide to let me deploy files.
If I do get past the above hurdles, it won't then let me run or debug the
files. It just hangs and eventually gives up.
I have built an emulator version (ARMV4I, version 3) and Visual Studio
connects and deploys to this fine. However, it also suffers from the same
run/debug problem except this time it gives me an immediate error message
"The remote computer does not have CLR version which is compatible ...".
If I physically copy the files to the device using ActiveSync and run this
then the program runs in the .net framework as expected.
I have tried adding in other components, new platforms, CoreCon, and both
CF2 and CF3.5. No difference.
1. Why does it take an eternity to connect and deploy to a real device with
Visual Studio, if it succeeds at all?
2. Why won't let me Visual Studio debug a program - what WinCE components
am I missing? I can run a program using CTRL-F5.
I have read some of the information in this thread and can confirm edm2.exe
is running as a process when I hit this problem.
Thanks in advance for any help.