I suggest you ...

When you remove a breakpoint while debugging, it stays removed.

Many times while debugging a developer will find a breakpoint they don't want, and they'll remove it. Minutes later while debugging again, they'll be faced with the same breakpoint, and they'll, in frustration, remove it again, only for it to be back!?

Yes, we can remove the breakpoint once we're done debugging, but sometimes those files aren't open anymore because the debugger took us to other code files.

There needs to be a way to kill a breakpoint, while debugging, that removes it fully. Full stop.

18 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    Why voting is closed? Maybe this bug was fixed? The reason is to save your time as no one at Microsoft will ever look at all these votes. This is the way they ask for feedback and fix bugs

Feedback and Knowledge Base