-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support VSCode's Debug Adapter Protocol #1
Comments
Hello! Thanks for the suggestion 😃 |
Any progress on this front ? |
Implementation is mostly finished (in our internal repo). It may take up to several weeks to release the code to the public. |
@mickaelistria @eloraiby The change has landed in the repo, please check if it works for you. You can use the guide here https://github.com/OmniSharp/omnisharp-vscode/wiki/Attaching-to-remote-processes but set |
Thanks for this. |
I could try it and get the dotnet debugger working over the Debug Adapter Protocol in Eclipse IDE ! |
I've made a demo video about this integration: http://www.screencast.com/users/mistria/folders/Default/media/23b83e66-6219-4ca8-89fd-1a1cf245aa48 and tweeted about it https://twitter.com/mickaelistria/status/1016269152296820736 |
In order to make this debugger easily usable in VSCode and other IDEs (such as Eclipse IDE) supporting the VSCode Debug Adapter Protocol ( https://github.com/Microsoft/vscode-debugadapter-node/tree/master/protocol ), it would be nice to provide the option ot have netcoredbg read/write content conforming to this protocol.
For example, vsdbg has a
vsdbg-ui
executable which talks over the debug protocol instead of starting gdb console; and OmniSharp simply uses it as debugger in VSCode, which is then able to do most of the work: https://github.com/OmniSharp/omnisharp-vscode/blob/4dd381fa5e4b1e81266d4796d641d1bf2785d2c8/src/coreclr-debug/activate.ts#L155The text was updated successfully, but these errors were encountered: