omnisharp-vim VS nvim-lsp-installer

You can probably use omnisharp-vim (OmniSharp is the same tech that powers VS Code's C# experience).

https://github.com/OmniSharp/omnisharp-vim

https://github.com/OmniSharp/Omnisharp-vim is a thing, but I don’t know how good it is. I would probably go with VSCode or Rider (and their respective Vim plugins), as they are quite productive for .NET.

With respect to C#, have you looked at the [OmniSharp](https://github.com/OmniSharp/Omnisharp-vim) plugin?

Then use this if you don't want to use VS Code.

There's a language server for vim (and neovim): https://github.com/OmniSharp/Omnisharp-vim

Are you using omnisharp-vim? It works well in my neovim setup and configuring it was pretty straightforward!

I'm not sure if you are using the omnisharp command as an example or something you'd like to be able to do, but if it's the latter check out omnisharp-vim! I use it as my LSP for C# development and it integrates most all of omnisharp's functionality with neovim very well.

So OmnySharp has a help document „integrated“. Just type :h omnisharp-vim into vim and you should see it. Alternatively you can go to https://github.com/OmniSharp/omnisharp-vim/blob/master/doc/omnisharp-vim.txt and look at it there. In general: if a plug-in provides documentation, it’s probably stored under /doc/.txt As the c# langauage server is not a vim plug-in, it does not follow this standard. So I unfortunately can’t help with that.

I had previous gotten a working setup with https://github.com/williamboman/nvim-lsp-installer however, I have been unable to get it working ever since.

The only way to stay up to date, is when you read the commits if you update the plugins. In this case for the lsp-installer in the commit bfa74f4 was mentioned that the plugin will no longer maintained

A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig

We have now migrated from nvim-lsp-instasller to mason which provides automatic LSP and null-ls configuration after installation

nvim-lsp-installer or mason.nvim. FYI lsp-zero also uses mason.nvim for managing installation.

I'm using nvim-lsp-installer it installs typescript when installing volar. So I had given it that path. Plus I had typescript locally installing since I'm using vue3+ts(vite) template

Though mason only recently replaced nvim-lsp-installer. Same author but they decided to make a complete rewrite given the broader scope beyond only providing language servers. And nvim-dap had it's initial release in late July. The actual dap servers are all kind of mature since they've been running on vscode for a couple of years or more now - and the protocol is apparently almost as old as lsp. So when I call them beta, it's more a commentary on the state of the neovim side of the ecosystem. If you mess around getting nvim-dap to work then there's a chance things might change over the coming months and you might have to return to configuring it more often than you'd like. In this sense for now I'm happy just to open vscode or another more appropriate IDE to debug. But I can see myself using the plugins in a year or two when they've matured.

Here are a few resources to get you started: 1. https://github.com/neovim/nvim-lspconfig 1. https://github.com/golang/tools/tree/master/gopls 1. https://github.com/williamboman/nvim-lsp-installer

Can recommend a combination of omnisharp-roslyn native LSP (installed manually or through something like mason or nvim-lsp-installer) with omnisharp-vim for some extra C#-niceties like OmniSharpRunTest, etc.