Comment by anonymars
3 months ago
> to debug multiple binaries simultaneously in the same solution requires launching multiple instances of the entire IDE
Eh? https://learn.microsoft.com/en-us/visualstudio/debugger/debu...
> complicated and unmodifiable shortcut keys for common tasks. Killing the proces
https://learn.microsoft.com/en-us/visualstudio/ide/identifyi...
Debug.TerminateAll is right there in the list
> No you’re just completely ignorant
Forgive my skepticism
The keyboard layout change is not on my version (dogfood) for some reason, maybe because I have to use Remote Desktop and it doesn’t detect a physical keyboard. But fine, I’ll take that back. I even asked AssPilot for help and it was predictably useless.
And cmon modify the registry to debug multiple processes? People work together in teams and share a common tooling that ideally tries to minimize the friction required to get work done. Think about that while contrasting the steps required in that article with the alternative of“launch the app a couple more times, then…”
Huh? The registry thing is for a specific niche*, not just "multiple processes"
You just set the startup properties on the solution to start the multiple projects. On that page, look for "To set the startup project or multiple projects from solution Properties" (https://learn.microsoft.com/en-us/visualstudio/debugger/debu...)
* "Sometimes, you might need to debug the startup code for an app that is launched by another process. Examples include services and custom setup actions"
Starting multiple copies of the IDE wouldn't handle these scenarios either
Fair enough, but still way more complicated than doing ‘make debug’ more than once