Debugger auto connect

[HenrysHouses]

Im not entirely sure i tried the latest version but last time i tried the debugger didnt auto connect. I assume its on the list of things to get done, but it would be nice as its one of the tools i use a lot instead of printing. If its already in and i just missed it then just ignore this and let me know

[walcht]

It is already mentioned here: walcht/unity-dap#3

Thing is: Unity has 0 documentation on how to do it - but there is a UnityProbe.dll in the official vscode extension that does exactly this (figure out the port Unity's debugger is listening on). I have to decompile it and look how they do it...

[HenrysHouses]

Oh right i remember. Also this isn't as related so maybe it could be its own issue if you don't have an answer. But i was talking to someone who was trying to setup roslyn for unity and neither me nor them were able to get full workspace diagnostics working in a qflist, only open files. Supposedly its an lsp config issue as roslyn.nvim should have the features to do it but I havent looked too closely on this yet

[walcht]

Just to be sure - you have something like this in the setting?

  -- Roslyn-LS-specific settings
  settings = {
    ["csharp|background_analysis"] = {
      dotnet_analyzer_diagnostics_scope = "fullSolution",
      dotnet_compiler_diagnostics_scope = "fullSolution",
    },

Otherwise please do open a new issue in this repo (thank you).