Skip to content
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

Alternative debugger using #2973

Closed
AndreyZWorkAccount opened this issue Apr 8, 2019 · 4 comments
Closed

Alternative debugger using #2973

AndreyZWorkAccount opened this issue Apr 8, 2019 · 4 comments
Labels

Comments

@AndreyZWorkAccount
Copy link

AndreyZWorkAccount commented Apr 8, 2019

Hi guys,

I want to try the debugger using VS Code. The debugger supports VS Code Debug Adapter Protocol, so I'm wondering if there is a way to use the debugger through your extension ( sorry if I said something wrong ).

Is it possible to use my own Debug Adapter Protocol implementation instead of 'vsdbg-ui.exe'?

Best regards,
Andrey.

@ExceptionGit
Copy link

Can help VSCodium/vscodium#82

@rchande
Copy link

rchande commented Apr 8, 2019

cc @gregg-miskelly ?

@gregg-miskelly
Copy link
Contributor

gregg-miskelly commented Apr 8, 2019

The way debug adapters work in VS Code is that the type property in your .vscode/launch.json file tells VS Code what debug adapter to use when you hit F5. So if someone provided an alternative debug adapter that worked with .NET Code, you could modify the type property in your launch.json to use that debug adapter. I am not familiar enough with Samsung's debug adapter to know if it is a candidate to be such a debug adapter. But the .NET Core debugging APIs are available for anyone who wants to try and create an alternative.

@AndreyZWorkAccount
Copy link
Author

@ExceptionGit, @gregg-miskelly Thank you for help! I've reached my goal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants