✅ Problem build.sh omnisharp-roslyn
Apparently there are a vulnerability in the package Microsoft.AspNetCore.Server.Kestrel.Core in version 2.2.0 which cause an error when I try to build the LSP server. The vulnerability was solved in the version 2.3.6 of the package but also show's some errors if I modify the Directory.Packages.props version of the package. I'm using Linux so don't know to much about C# environment. Any advice about updating packages with nuget/dotnet?
14 Replies
Why are you trying to build O# at all?
For fun
But... why
What lead you down the path of building O# in the first place
Just to see how to build the tool, keep the repo in my OS in case I want to change version
This is why I'm asking you why
also with it I notice that NuGet downloads packages directly for projects, but in this case is different and don't know why it does not change by moving what I though was a config file for packages
What is making you think you need O# at all
ahhhh sorry O# is omnisharp right? haha
I want to attach it to my neovim
Don't. Use roslyn
If you search in this discord for neovim, you'll find a lot of examples of people getting it set up for C# work
roslyn? pure roslyn?
Yes
okay I'll search some examples
ty
Searching i've found a mention to the repo seblyng/roslyn.nvim, quick configuration just adding repository to mason and to Lazy.nvim.
Mason only offers the O#_roslyn from the lsp-config list. To add the roslyn just follow the repo instructions. Left the link to the repo if someone needed
https://github.com/seblyng/roslyn.nvim
GitHub
GitHub - seblyng/roslyn.nvim: Roslyn LSP plugin for neovim
Roslyn LSP plugin for neovim. Contribute to seblyng/roslyn.nvim development by creating an account on GitHub.
GitHub
GitHub - SofusA/csharp-language-server: A wrapper around Roslyn lan...
A wrapper around Roslyn language server which makes compatible with editors other than VSCode - SofusA/csharp-language-server