Why does F10 (step over) in Visual Studio not work?

Question

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?

Solution 1

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

Solution 2

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

Solution 3

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.

Comments

[TheSoftwareJedi]

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.

[edosoft]

Thanks!! I'll install and report back

[Powerlord]

@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.

[Arne Claassen]

Fixed the problem for me. Most appreciated

[adambox]

here's the link for the fix (Visual Studio 2008) code.msdn.microsoft.com/KB957912

[Groo]

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.

[Vitaliy]

Not sure why the step into is better. I have the situation as TS both F10 and F11 doesn't work.

[logixologist]

I’ll take 10 or 11 at this point. It skips over many of them and it’s not related to that. I have used the commands on screen as well as a sanity check.