My Visual Studio 2008 IDE is behaving in a very bizarre fashion while debugging a unit test: I have a breakpoint and when I hit it and then try to step with F10 the test con
Are you putting your breakpoints inside code that is part of a generated class?
I have experienced this problem on the client site of a service reference. The generated classes are partial classes with the
[System.Diagnostics.DebuggerStepThroughAttribute()]
attribute applied. Even when my breakpoint was in a different file, but still part of the attributed class, the breakpoint would be skipped.
I removed that attribute from the generated Reference.cs file and the debugger worked as I expected.
Of course, this isn't a permanent solution because if the Reference.cs file gets regenerated, the attribute comes back.