Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

13
  • 1
    I've got this configuration and I cannot reproduce your stated behavior. Would it matter that I'm using Win7 64 Bit SP 1? The rest of the setup is the same, but I hit the breakpoint every time.
    – Bob G
    Commented Apr 21, 2011 at 13:13
  • 2
    I imagine the line has been optimised out by the compiler if you step it, is it running the console.writeline("1") twice, but supplying different arguments?
    – forsvarir
    Commented Apr 21, 2011 at 13:15
  • 2
    @CuiPengFei: You're right, it's odd... if you put the breakpoint on the actual call to WriteLine (in the disassembly view), then it does get hit, but you have to keep reenabling it for each run.
    – forsvarir
    Commented Apr 21, 2011 at 13:31
  • 2
    @CuiPengFei: What I think is even odder, is if you duplicate the final Console.WriteLine (copy it to the line below), you can set the breakpoint on the last one and it will be hit, but the one with your current breakpoint on it still won't be...
    – forsvarir
    Commented Apr 21, 2011 at 13:37
  • 1
    This looks like a job for connect.microsoft.com. Commented Apr 23, 2011 at 15:35