Problems debugging

[Frederik Jensen]

I have a very persistant problem: whenever I start my VB.NET CF application
from VS.NET2003 using the debug command (F5) the device stalls for a couple
of minutes and exits the loading of the program. No startform appears on the
device. I have worked around it relying on messageboxes as I cannot figure
out why the debug environment will not work. VS.NET output lists successfull
build and launch of application.

I have testet with three different models with same result (Symbol
PPT8800/windows mobile, Symbol VRC8900/ce4.1, Advantech MobiPanel/ce4.2).

Any experiences or thoughts. Any comment appriciated.

 

[Sergey Bogdanov]

It seems that \windows\toolhelp.dll is absent. You can find it in:
CompactFrameworkSDK\WinCE Utilities\ToolHelp\WinCE4\

Best regards,
Sergey Bogdanov

 

[Frederik Jensen]

It seems that \windows\toolhelp.dll is absent. You can find it in:
CompactFrameworkSDK\WinCE Utilities\ToolHelp\WinCE4\

Thanks, but the attempt was unsuccessfull.

I copied C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\WinCE Utilities\ToolHelp\WinCE4\armv4\ToolHelp.dll
to \Windows\ToolHelp.dll. I attempted the same with all arm-CPU versions of
toolhelp and the CPU type is set to either ARMV4 or ARMV4T.

I have read the readme file and checked that all bullets in the section
"What does my device require to debug with Visual Studio?" apply: 1) I have
a ActiveSync connection (3.7.1), 2) \Windows\wceload.exe exists, 3)
\Windows\ToolHelp.dll exists.

My device lists processor type Intel Corp. ARM-XScale and in VS.NET I set
CPU type to ARMV4.

I attempted to setup a TCP connection following "How do I deploy and debug
my application on a device running Windows CE with TCP/IP support?" Also
with no success.

I am very frustrated with the debug situation. I have made severel attempts
monts apart, however, I have not found a solution to enable/reeanble debug.
Why must it be so difficult?

 

[Guest]

I had the same problem and I solve it today by changing the CPU type in
VS.net to
ARMV4T and then restarting VS.NET.

 

[Frederik Jensen]

I had the same problem and I solve it today by changing the CPU type in
VS.net to
ARMV4T and then restarting VS.NET.

I changed the CPU type to ARMV4T and copied the corresponding ToolHelp.dll.
VS:NET output window:
*Launching Application
*Error while trying to run project: Unable to start debugging.

*Unable to start program
'C:\PHI\DOTNET\SmartDeviceApplication11\bin\Debug\SmartDeviceApplication11.exe'.

Attempted same with ARMV4I that automatically switches back to ARMV4T.