Permanently remove a breakpoint in Visual Studio during debugging - by Michael Freidgeim

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 391642 Comments
Status Closed Workarounds
Type Suggestion Repros 5
Opened 1/8/2009 2:40:34 AM
Access Restriction Public


During debugging, if I remove breakpoint, it's temporary removed, but appears again in the next debugging section. 
It can be deleted only from the breakpoints window. The behavior is very annoying.
Can the breakpoint be permanently removed by click the red circle (or press F9)?
The same issue discussed at
Sign in to post a comment.
Posted by Cine on 9/11/2014 at 11:12 PM
Even VS2013 didnt solve this super annoying problem... Atleast add a confirmation to remove ALL instances when there ARE more.
Posted by IanBoyd on 7/10/2014 at 10:29 AM
So that's why removing a breakpoint doesn't remove a breakpoint.

It's a 'feature'.
Posted by JackAtWork on 5/2/2014 at 8:02 AM
Super annoying
Posted by ebol2000 on 1/16/2012 at 5:24 PM
I agree with Edgar. Please remove this feature, or make it a new optional featured defaulted to off in case there are a couple of developers around who want this feature.

Eric B
Posted by Edgars Batnya on 8/10/2011 at 3:37 AM
This feature needs to get lost.
Posted by danq m on 5/12/2011 at 1:42 PM
Andrew, can you reopen this as a bug report? I consider this a major usability flaw. At the very least, there should be a setting to disable this behavior.
Posted by Microsoft on 1/23/2009 at 2:45 PM
Hi Michael,

Thanks for the feedback, we greatly value customer feedback on issues like this, and we will definitely take this suggestion into consideration for future releases of Visual Studio.

Posted by Michael Freidgeim on 1/20/2009 at 6:51 PM
Thanks, Andrew for your reply.
You described the behavior correctly, but it is not a bug report, but the suggestion to have an ability using short-key and context menu to delete breakpoints without opening breakpoints window.
E.g can user in options configure that F9 will delete one or all breakpoints for specified line?
Posted by Microsoft on 1/20/2009 at 5:26 PM

Based on your description of the problem, we believe this issue results from the fact that the breakpoint has been bound in multiple places, and therefore when you remove it from the editor margin there are other breakpoints that are still queued to be hit. When you see this behavior, please open the breakpoints window (Debug -> Windows -> Breakpoints) and if a "+" appears next to the breakpoint that is not being permanently removed, this indicates it has been bound in multiple locations. Deleting the breakpoint from the breakpoints window in this scenario will fix the problem.

For now I'm going to close the bug as "By Design". If the behavior I have described is not the issue that you are seeing, please re-active this bug and include detailed steps for reproducing the problem (preferably with an attached project) so we can better understand what you are seeing.

Best Regards,
Andrew Hall
Visual Studio Debugger