W
Walt D
Hi... I am part of a 12-member development team, and we are ALL having
this problem. We are developing an application for the PocketPC using
the .Net Compact Framework 2.0 and Visual Studio 2005. We are using the
PocketPC emulator included with Visual Studio and can successfully
connect to the emulated PocketPC using ActiveSync.
Our problem is that every time we tell Visual Studio to launch the
application (either start with debugging or without), it re-installs
the Compact Framework on the PocketPC. This takes 5-10 minutes and thus
makes debugging extremely impractical. Our current solution is to set
up a shared folder between the PocketPC and the development PC and copy
the executable file there, but we cannot use the debugger to step
through our code in this way.
Does anyone have any solutions to this problem? Thanks for any
assistance.
- Walt
this problem. We are developing an application for the PocketPC using
the .Net Compact Framework 2.0 and Visual Studio 2005. We are using the
PocketPC emulator included with Visual Studio and can successfully
connect to the emulated PocketPC using ActiveSync.
Our problem is that every time we tell Visual Studio to launch the
application (either start with debugging or without), it re-installs
the Compact Framework on the PocketPC. This takes 5-10 minutes and thus
makes debugging extremely impractical. Our current solution is to set
up a shared folder between the PocketPC and the development PC and copy
the executable file there, but we cannot use the debugger to step
through our code in this way.
Does anyone have any solutions to this problem? Thanks for any
assistance.
- Walt