J
jcavo
Hello,
Ever since I stalled CF2.0 SP1, I've encountered this strange behavior:
When pressing F5 to debug my Smart Device Windows CE 5.0 project (VS2005
connects to my device alright), the error message "Unable to Start Program
"%CSIDL_Program_File%\DeviceApplication1\DeviceApplication1.exe" will
appear. To fix this problem, I have to go through the following steps:
1.Project -> Properties->Devices and UNCHECK "Deploy the Latest Version of
the .NET Compact Framework (including Service Packs)"
2.Press F5 and everything works without the error message
3.Project -> Properties->Devices and CHECK "Deploy the Latest Version of the
..NET Compact Framework (including Service Packs)"
4.Pressing F5 will always work from here on.
So now for a newly created project I have to uncheck the "Deploy the Latest
Version...." box and run the debugger once. After that whether the box is
checked or not doesn't matter anymore and everything seems to work just
fine. This behavior only happened after I installed SP1. It was frustrating
for a while until I found this work around. I'll appreciate it if anyone
has insights into this strange behavior of VS2005/CF2.0.
Thanks
Ever since I stalled CF2.0 SP1, I've encountered this strange behavior:
When pressing F5 to debug my Smart Device Windows CE 5.0 project (VS2005
connects to my device alright), the error message "Unable to Start Program
"%CSIDL_Program_File%\DeviceApplication1\DeviceApplication1.exe" will
appear. To fix this problem, I have to go through the following steps:
1.Project -> Properties->Devices and UNCHECK "Deploy the Latest Version of
the .NET Compact Framework (including Service Packs)"
2.Press F5 and everything works without the error message
3.Project -> Properties->Devices and CHECK "Deploy the Latest Version of the
..NET Compact Framework (including Service Packs)"
4.Pressing F5 will always work from here on.
So now for a newly created project I have to uncheck the "Deploy the Latest
Version...." box and run the debugger once. After that whether the box is
checked or not doesn't matter anymore and everything seems to work just
fine. This behavior only happened after I installed SP1. It was frustrating
for a while until I found this work around. I'll appreciate it if anyone
has insights into this strange behavior of VS2005/CF2.0.
Thanks