Debugging via ActiveSync

  • Thread starter Thread starter LightStamp
  • Start date Start date
L

LightStamp

I've got an existing CE5 application that i will maintain. I'm running the
app from VS2005 and deploying to the device. I've set a breakpoint in a
module and hit F5 and get "the breakpoint will not currently be hit. The
specified module has not been loaded."
How do I enable this breakpoint during runtime for debugging?

In desktop apps I've had to add a reference say to another DLL but this
module is in the project.

TIA
Harry
 
Is your project running in Debug mode? If you are compiling for Release,
then the executable will not have the symbolic information required to hit
the breakpoint.

Dick

--
Richard Grier, Consultant, Hard & Software 12962 West Louisiana Avenue
Lakewood, CO 80228 303-986-2179 (voice) Homepage: www.hardandsoftware.net
Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004, Revised July
2006.
 
Think part of the problem is I've never debugged a CE 5 app like this only
Pocket PC apps and I hear debugging is different for this OS. I just want
to debug to the device though so seems like it ought to be possible.
 
I've got an existing CE5 application that i will maintain.  I'm runningthe
app from VS2005 and deploying to the device.  I've set a breakpoint in a
module and hit F5 and get "the breakpoint will not currently be hit.  The
specified module has not been loaded."
How do I enable this breakpoint during runtime for debugging?

In desktop apps I've had to add a reference say to another DLL but this
module is in the project.

TIA
Harry
Click to expand...

I've run into this before if my target platform did not match my
device type. For instance I have a winmo5 project that I can debug
with breakpoints on a Dell Axim X51 (Winmo5), but debugging fails with
on a winmo6 iPaq device.

You may need to change your target platform. In Solution Explorer,
right click the project name and choose "Change Target Platform" near
the bottom of the context menu. Make sure you have the correct
windows mobile SDK that matches your hardware os version.

Regards,
Russ
 
Back
Top