I should also note, I haven't written much lua code before, so there's a chance I made some rookie mistakes or wrote things in a way that could be improved. Please don't be afraid to say so if this is the case anywhere!

@PowerUser64 I've pinned your repo in my config to test this out, but I'm not having much luck. I have a solution with upwards of 70 .csproj projects in it. When I open Compiler and choose to build, it reports

MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.

I was hoping it would build the project in which the current file resides. Is this what should be happening? Or do I need to specify the project somehow? I've tried running the build command with a .csproj as the active buffer as well to no avail.

Any help would be appreciated. Thanks for all your work on this!

Thanks for testing this out! I have not tested this with projects that are quite that large, so I don't think I can solve this on my own. Although, it probably wouldn't be too difficult since you have an environment for it.

It sounds like you need to add some code that can detect which csproj project you want to compile, which you can do somewhere in here (the file should be at ~/AppData/Local/nvim-data/lazy/compiler.nvim/lua/compiler/utils-bau.lua, assuming you're on windows and using lazy.nvim as your plugin manager). This is the code that builds the msbuild command.

All you would need to do is add a way for compiler to get the csproj you want and provide it as an argument to msbuild. The basic command it generates right now is MSBuild.exe -t:Build -p:Configuration=Debug (with some variance depending on whether you run, build+run, clean, etc.). You would need to add a way to specify what csproj file should be used.

It might be necessary to generate compile commands for the entire list of csproj files accessible through the .sln and make entries for each of them in the compiler menu. I work mostly with smaller vcxproj projects rather than csproj so I can only offer limited help on this one.

If you find something that works though, feel free to make a PR to the msbuild-init branch on my fork of compiler.nvim and maybe we can get it merged here too! At least, we'll increase neovim's support for M$'s dev tooling another 1%. It's very poorly supported with nvim from what I've found, so anything helps.

In fact, if you use anything that helps you work with msbuild (or related ms tools), I would love to know, since I feel like I'm one of the only ones on the planet interested in doing this, and you're the only other one I've heard of trying to do this 😂. Personally, I've started using overseer.nvim in my config a bit, without going through compiler in some cases (compiler.nvim is a wrapper for overseer in a lot of ways), which has helped me gain some more control over it.