Visual Studio Debugger Breakpoint Helper

Your Breakpoint Is Bound, But Doesn't Hit

The solid red glyph indicates your breakpoint has bound at least once, so it should fire. There are various further possibilities:

Multiple Instances

The breakpoint might not have bound to the correct instance. Check the Breakpoint Window and see if the breakpoint has a '+' sign on it. If it does click on it to see if multiple instances arose from your breakpoint.

Source Path

If you have multiple source files of the same basename but different paths (e.g. c:\project\test.cs and c:\another\test.cs) then the debugger may be using the wrong one. Use the Source File Paths setting (via Solution Properties) to get the debugger to ignore the bad source file and only use the good one. This can also happen when the same source file is used in multiple binaries, in which case see Multiple Instances above.

Multiple Processes

If you are debugging more than one process then again this can cause problems. Use the Breakpoint Window to show additional columns, such as Program, to show additional information for your breakpoints.

Issues With Managed Breakpoints Randomly Stopping Working

We have investigated cases where managed breakpoints bind and sometimes stop, but then fail to stop, when managed debugging. Right now we have not determined the full cause (or a work-around).

Breakpoint Helper Has Finished

Did this solve your problem? Yes or No

Click here to start the breakpoint helper again.

This is a prototype, please send general feedback