Isn't `vsdbg` still distributed with an incredibly restrictive license? Doesn't sound all too open to me.
Further, the twitter posts themselves are still relevant I believe. If someone took over my repo, I'd remember it 3 years later.
Further, the twitter posts themselves are still relevant I believe. If someone took over my repo, I'd remember it 3 years later.
So far, there was little demand to write another debugger integration (because, really, the debugger core is implemented in the runtime itself - what vsdbg, NetCoreDbg and Rider all primarily do is consume the runtime API).