Can't debug

[Graham McKechnie]

Hi All,

I was wondering if anyone has any suggestions of how to fix my debugging
problem.

Up until a couple of days ago, I've always been able to debug a program and
stop on any line I choose. But since delivering the program to the client,
I've now come back to make some changes and no matter what I do, I can't get
the IDE to go into debugging mode.

I've changed both exe's of the two projects in the solution from release to
debug, but neither enter will enter debug mode. The best I get is deploying
the app, launching the app, the hour glass appears on the device, but then
nothing the app doesn't run and consequently I never reach the breakpoint.
This happens with both projects.

I'm sure I've done something dumb, but just can't figure it out. If I just
run the apps, they both run fine - its just appears to be debugger.

Graham

 

[Mono]

Graham,

First: I'm not going to help you!
Second: You are not alone!


Every day I start VS with a fear of not being able to debug my applications.
It's totally random: several days the debugger is "working" then 2-3 days is
not, then again everything seems ok, then .... total mess!

Zarko

 

[Ginny Caughey [MVP]]

Hi Graham,

Are you trying to debug to the emulator or the device? Have you tried
resetting whichever one it is? Can you deploy ok but just not debug?

 

[Graham McKechnie]

Ginny and Mono,

I've got the debugger working again. I built a new app with the wizard and
just compared all the settings. For some reason my Enable Remote Debugging
was on by default. Don't know how, but as soon as I made that false the
debugger worked again and thankfully has been working all day. By the way
because of the rapi stuff, I've given up working with the emulator, its been
just the device for a couple of weeks now.

Ginny its starting to remind me of VO and its repo problems.

I think my problems started last week when I moved some code that is shared
by the 2 exes in the solution into a separate solution to create a dll. I
need to supply the source code to this client, but I didn't want to give him
the generic classes that I developed independantly of this project, so I
thought the easiest way to do that would be to move that code into a
different solution to create the dll.

When I first did that, I then had all sorts of trouble with compiler errors
trying to get it all together again. In desperation I decided to copy the
whole dam lot to another drive and then blow away the existing Solution and
built a new one from scratch bringing in .cs files one at a time. I got it
all built that way and delivered to the client, but hadn't tested with the
debugger.

I haven't gone back and turned remote debugging back on, so I don't really
know if I fluked it - will test again when these latest changes are
finished. But Mono you might want to check that setting in your solution.

If anyone else can second guess this problem and how it originated - I'd
like to hear, because I'm sure I didn't turn on remote debugging.

Regards
Graham

 

[Ginny Caughey [MVP]]

Hi Graham,

I've got the debugger working again. I built a new app with the wizard and
just compared all the settings. For some reason my Enable Remote Debugging
was on by default. Don't know how, but as soon as I made that false the
debugger worked again and thankfully has been working all day. By the way
because of the rapi stuff, I've given up working with the emulator, its been
just the device for a couple of weeks now.

Thanks for this info.

Ginny its starting to remind me of VO and its repo problems.

I think my problems started last week when I moved some code that is shared
by the 2 exes in the solution into a separate solution to create a dll. I
need to supply the source code to this client, but I didn't want to give him
the generic classes that I developed independantly of this project, so I
thought the easiest way to do that would be to move that code into a
different solution to create the dll.

When I first did that, I then had all sorts of trouble with compiler errors
trying to get it all together again. In desperation I decided to copy the
whole dam lot to another drive and then blow away the existing Solution and
built a new one from scratch bringing in .cs files one at a time. I got it
all built that way and delivered to the client, but hadn't tested with the
debugger.

I haven't gone back and turned remote debugging back on, so I don't really
know if I fluked it - will test again when these latest changes are
finished. But Mono you might want to check that setting in your solution.

If anyone else can second guess this problem and how it originated - I'd
like to hear, because I'm sure I didn't turn on remote debugging.

It does sound like moving the project was the source of the problem, but I
don't know why Remote Debugging would be changed.

Ginny Caughey
..Net Compact Framework MVP