csharp-language-server VS omnisharp-roslyn

The recommended approach used to be coc-omnisharp, but it has been discontinued in favor of chsarp-ls. I have installed csharp-ls with dotnet tool install --global csharp-ls, and the executable is on ~/.dotnet/tools. The following is on my coc settings:

I switched to https://github.com/razzmatazz/csharp-language-server which doesn't have as many features.

Apropos lsp, these two might be interesting, if you haven't yet given up on C#. Again, that should work on many editors, including the evil one at hand. Note how both explicitly name vim, emacs and vscode in their documentation.

It using lsp protol.i tried the new version of omnisharp with lsp but its really bad, 2 client extension if you don't want to use omnisharp https://github.com/statiolake/vscode-csharp-ls And https://github.com/vytautassurvila/vscode-csharp-ls And last, server lsp https://github.com/razzmatazz/csharp-language-server

lol quite specific. do you know https://github.com/razzmatazz/csharp-language-server ?

There's Saulius's lsp too too, altogh I haven't tried it yet.

You could also set the semantic tokens capability to nil. Another alternative to omnisharp is csharp-language-server which has recently added support for semantic tokens.

I ended up using csharp_ls, https://github.com/razzmatazz/csharp-language-server/issues/34 posted what I found here. Once I got things pointing to the right mono dll it started working great.

Sadly, OmniSharp (the LSP for vscode and nvim) isn't all that great. The performance is incredibly bad, easily orders of magnitude worse than VS and Rider.

There is this alternative LSP, which I plan to try out still: https://github.com/razzmatazz/csharp-language-server

I don't know about your case, but wanted to add a comment. I had some problems recently with omnisharp, and someone recommended me to try https://github.com/razzmatazz/csharp-language-server instead of omnisharp, I switched and so far with no issues.

Apropos lsp, these two might be interesting, if you haven't yet given up on C#. Again, that should work on many editors, including the evil one at hand. Note how both explicitly name vim, emacs and vscode in their documentation.

I've been using Neovim (on Windows, not WSL) with Unity and the Omnisharp LSP smoothly for a while now, and it's definitely possible to have a decent experience. Assuming your config is already setup for LSP, completion, snippets, etc., there are a few Unity/Omnisharp specific workarounds to be aware of:

I solved it using the workaround at the end of this issue thread in omnisharp-roslyn

See: https://github.com/OmniSharp/omnisharp-roslyn/issues/2483 for some solutions.

No, Sematic Tokens has an issue opened for it since Dec 2022, with couple (well, at least one that I have seen) PRs open trying to fix it and some hacking around the issue in the comments, but it's not solved afaik.

Have a Look at this

I think the issue is related to 'Semantic Tokens' introduced in version 0.9 https://github.com/OmniSharp/omnisharp-roslyn/issues/2483

I did, but it's a little bit tricky. If you could wait some hours I will share it with you after work. You can take a look at this thread first: https://github.com/OmniSharp/omnisharp-roslyn/issues/2250