csharp-language-server VS omnisharp-extended-lsp.nvim

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.

I tried to add the omnisharp-extended repository to my Lazyvim config. As described on both lazvim-starter and the omnisharp-extended repo I added the omnisharp-extended handler to my omnisharp setup. In my old config this worked perfectly. But somehow I can't load the omnisharp-extended plugin. I added it to the config and I see it installed when checking Lazy, but when I try to run require("omnisharp-extended") I get a module not found. Therefore my omnisharp setup doesn't work either. First I thouthg it could be a problem because of lazyloading, but even if I set lazy = false I can't require it.

Definitely possible with this plugin: https://github.com/Hoffs/omnisharp-extended-lsp.nvim