views:

1249

answers:

8

I'm debugging a (web) project in Visual Studio 2008. I'm hitting a breakpoint. F10 continues to the next line, as expected, but the next F10 just stops debugging and the code continues without any more debugging (like pressing F5). Why is this happening?

  • I have tried 'clean solution'.
  • Other breakpoints sometimes(!) skipped, even in the same method

Any clues?

A: 

Make sure that you're in Debug mode not in Release.

Vadim
Checked this, thanks.
edosoft
A: 

Without knowing more about your application it's difficult to say, but usually this sort of thing happens when the process starts a thread or otherwise goes into code where there isn't any debug information.

ChrisF
A: 

and make sure your code is reachalbe

Ada
and you can use even F11
Ada
A: 

There could be an exception while executing the instruction in question. Try enabling all exceptions to break into debugger and check.

Canopus
A: 

Hi

It almost sounds like you have the default settings for your debugging. If you go to: Tools
- Options - Debugging Under the general section there is a option to "Enable Just My Code" By default that is checked, if you uncheck that you should be able to step into the code that you want to see.

Without knowing more about your project and code that you reference, this is my best guess as to why you can’t step into the code.

Hope it helps Rihan

Rihan Meij
+1  A: 

F10 is Step Over. This means that any methods called by your current method will not be shown in the debugger. If these throw an uncaught exception or somehow end execution, debugging will just end, which would result in what you are experiencing.

F11 (Step Into) is usually a better idea when stepping through code.

R. Bemrose
He didn't say he wants to step in - he said he wants to step over. Saying F11 is better than F10 is just not right.
TheSoftwareJedi
@TheSoftwareJedi: Really? Did you read the question name? "Why does F10 (continue) in Visual Studio not work?" The reason being because F10 isn't Continue.
R. Bemrose
A: 

It might be stepping over the last executing code in the thread or somehow it's going back to the UI thread. If it's a GUI app, try doing something that invokes an event handler and see if it breaks on the next execution.

Davy8
It's a web app
edosoft
ah I see, I don't know then
Davy8
+11  A: 

It is probably because you do not have the update kb 957912 for Visual Studio 2008. That fixed the same issue on my machine.

Alyn
Thanks!! I'll install and report back
edosoft
Fixed the problem for me. Most appreciated
Arne Claassen
Thanks for the solution, worked for me.
Carra
here's the link for the fix (Visual Studio 2008) http://code.msdn.microsoft.com/KB957912
adambox
Worked great for me also. I noticed it after reinstalling VS2008 in my fresh Win7 installation, I guess I didn't have SP1 on my previous machine? Whatever.
Groo