[jbosstools-issues] [JBoss JIRA] (ERT-593) C# debugging

[Mickael Istria (JIRA)]

     [ https://issues.jboss.org/browse/ERT-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Istria closed ERT-593.
------------------------------
      Assignee: Mickael Istria
    Resolution: Duplicate Issue


Dup of ERT-639.
netcoredbg seems like a good way to go, as it support gdb, mi and dap as interfaces. In Eclipse IDE, we'll go for the DAP interface.

> C# debugging
> ------------
>
>                 Key: ERT-593
>                 URL: https://issues.jboss.org/browse/ERT-593
>             Project: Eclipse Release Train
>          Issue Type: Enhancement
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>
> This ticket tracks long-term progress, investigation and possible actions about C# debugging on Eclipse IDE (or other non VS/VSCode IDEs).
> Current state is the vsdbg, which has support for debug adapter protocol (so it would be easy to consume in Eclipse IDE/Che) actually has a vendor lock which prevents it to start when not invoked from VS or VSCode.
> An alternative can be to follow https://github.com/Samsung/netcoredbg/issues/1 and use this debugger in place of vsdbg as soon as debug adapter protocol support is in.
> If we want to experiment another alternative that may work now, we can also try to write a VSCode extension that would start the vsdbg and simply forward streams. So the client (Eclipse IDE, Eclipse Che) could just create sockets and start `vscode` with some options (such environment variables) to have VSCode start vsdbg and connecting to the parameterized socket. Hopefully, as it would be VSCode invoking vsdbg, vsdbg would work and the extension would make vscode proxy would be a good server adapter for clients.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)