41 ms·
There's nothing inherent about the debugger that forces it to be in visual studio. There was a moment, circa 2016 or so, when it could have been opened and then
by phillipcarter 4y ago
There's nothing inherent about the debugger that forces it to be in visual studio. There was a moment, circa 2016 or so, when it could have been opened and then collaborated on with Jetbrains. Instead, MS leadership circled the wagons due to OSS FUD that they get sometimes, and Jetbrains was forced to build a better debugger that's also tied to its IDE.