Tell Visual Studio not to warn me when I edit while debugging

Question

Lately, VS has been getting more and more annoying about warning me about editing code while debugging. Regardless of whether it is a popup telling me that a file has been edited, purple underlining, or a warning that gets grouped with the compiler warnings and errors, I don't want it. I wish it would just let me edit, continue running the program that was built, and keep quiet about it.

Is there a way to tell it to do that?

Incidentally, I have already disabled edit and continue. See Edit and Continue: "Changes are not allowed when..."

Try [this](https://stackoverflow.com/questions/8174800/what-does-it-mean-require-source-files-to-exactly-match-the-original-version) — Eldar, Dec 09 '19 at 16:04

score 0 · Answer 1 · answered Dec 09 '19 at 16:07

0

You can apply changes to the source code in debug mode when you stop at a breakpoint.

Manual: How to: Apply Edits in Break Mode with Edit and Continue (Visual Basic)

answered Dec 09 '19 at 16:07

Streletz

192
3
15

score 0 · Answer 2 · answered Dec 21 '19 at 06:05

0

This is a workaround but some workarounds, well, work.

Run two instances of VS on the same solution. Debug one and encounter needed edit. Ctrl+TAB to the other instance and make the edit (without saving... by the way use auto-save). Continue until you’re done, and then save the files in instance 2. After debug, the changes are available to both instances.

Rarely (at least in my experience) do you actually want edit-and-continue; usually you’re watching the code under debug and realize it is wrong and want to fix it, but also want to see some downstream effects without killing the debug session.

This gives you that with a minor inconvenient task switch.

answered Dec 21 '19 at 06:05

Kit

20,354
4
60
103

That is, indeed, a solution. Whether it's worse than the problem is up to the user, I guess. – William Jockusch Dec 21 '19 at 13:35
1

VS *has* become more aggressive with edit/continue prompts. I've been getting these without *any* (afaik) changes to code. – Kit Dec 23 '19 at 17:07
Awarding the bounty, though this answer wouldn't work for my situation. But it might for some people. – William Jockusch Dec 26 '19 at 02:07

Tell Visual Studio not to warn me when I edit while debugging

2 Answers2