Basically the title, e.g. I have two different solutions in two different windows of Visual Studio, I run debugging on both. Then I stop debugging in one of them and it also stops debugging in the other one.
Also happens with Visual Studio Code – as if all the debuggers were linked somehow…
Question posted in Visual Studio Code
View the official documentation.
2
Answers
This turned out to be really obscure, but basically it was caused by a combination of settings in both Visual Studios.
Visual Studio 2022 was set to launch browser window on debug, and to stop debugging when the window was closed. Visual Studio Code also launched a browser window (to debug the app I am working on), and obviously that also stops debugging when the window is closed. So stopping debugging in either would close the browser window, thus stopping debugging in the other one.
You can try what is suggested here https://code.visualstudio.com/docs/editor/debugging under multi-target debugging.
Are you in multi-target mode when you launch multiple sessions?
You should be able to select the session from the Dropdown menu and click stop that way.
There’s another method under compound launch configurations as well.
Have you tried both these methods?