AstroNvim / AstroNvim/astrocommunity
.NET Multi Solution Detection
- Dominant language
- Lua
- Stars
- 1.7k
- Forks
- 313
- PR merge metrics
- No merged PRs in 30d
Description
### Checklist
- [x] I have searched through the AstroNvim documentation
- [x] I have searched through the existing issues of this project
- [x] I have searched the existing issues of plugins related to this issue
- [x] I can replicate the bug with the minimal `repro.lua` provided below
### Neovim version (nvim -v)
v0.11.3
### Operating system/version
Windows
### Terminal/GUI
PowerShell
### Describe the bug
I have been trying to use .NET with AstroNvim. It's very laggy and projects aren't being detected. I've tried using all plugins out there and there's no luck. I get the same bugs as mentioned. Typically I work in big repos and I used Roslyn as well to configure .NET. Is there anything that will be help me use AstroNvim with .NET smoothly or is there a nice alternative that uses vim? My productivity has not gone well thus far using .NET and AstroNnvim.
### Expected behavior
All solutions should be detected. I should be able to jump from one file in a separate solution to another and still have the same behavior.
### Screenshots
Detects here:
Jump to another file in seperate sln (no detection/everything breaks):
### Additional Context
_No response_
### Minimal configuration
`User.lua`:
```Lua
---@type LazySpec
return {
-- == Examples of Adding Plugins ==
{
"seblyng/roslyn.nvim",
ft = "cs",
opts = {
roslyn_path = "C:\\Users\\gihernandez\\AppData\\Local\\nvim\\roslyn-lsp\\Microsoft.CodeAnalysis.LanguageServer.4.8.0-3.23451.1.zip\\lib\\net7.0\\Microsoft.CodeAnalysis.LanguageServer.dll",
filewatching = "auto",
broad_search = true,
lock_target = false,
},
config = function(_, opts)
require("roslyn").setup(opts)
end,
},
```
Contributor guide
Research direction
Start with the provided User.lua and its roslyn.nvim setup, especially the filewatching, broad_search, and lock_target options. Reproduce the configuration on Windows with the supplied minimal setup, then verify that moving between files in separate solutions preserves detection and behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, lua, vim
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100