Closed wambldor closed 9 months ago
Thanks @wambldor. I believe you are free to name your adapter (i.e. the dap.adapters.
In reality, the name of the dap adapter being used should be a configuration value that can be passed in, given that it could literally be any value.
I'll use this issue to create a new option to pass this in, but for the time being, to get it to work, just change the name used in you own dap config to 'netcoredbg' instead of 'coreclr'.
Sorry, I didn't realize that the names of the dap adapters are freely selectable. Probably because I use mason-nvim-dap. There the names for the automatic installation are fixed.
If I find time I would like to create a pull request to make the name configurable.
No problem @wambldor . I had to double check it myself to confirm!
That would be a great help if you could raise a PR. I'm working on a large feature change at the moment, so that's keeping me busy! No problem if you don't find the time though. I will get round to this eventually.
Closing this as PR addresses it.
Hi,
I wanted to use the plugin for debugging UnitTests, but unfortunately the plugin seems to search for a debug adapter named
netcoredbg
. The debug adapter name should becoreclr
, as described in the nvim-dap repository. When debugging my application, my configuration with the name coreclr works.Thank you for the work on this plugin, we can use any plugin for .net support!