StyleCopAnalyzers VS omnisharp-roslyn

Several well-known NuGet packages such as xUnit.net, FluentAssertions, StyleCop, Entity Framework Core, and others include by default a significant number of Roslyn analyzers. They help you adhere to the conventions and best practices of these libraries.

I created a StyleCopAnalysers.ruleset file at the root of my project, which contains the ruleset for analysis. The tool not only identifies issues but also attempts to fix them, providing a log of any unresolved problems. In addition to running the analyzer upon build, the dotnet format command also runs any external analyzers that it detects by default as well.

https://github.com/DotNetAnalyzers/StyleCopAnalyzers the successor to stylecop - most of the rules ported over

I'm a C# guy, so that is what I care about. For .NET we do have StyleCop analyzers. And EditorConfig exists to help at the IDE level across all languages. And git itself can be configured with such things as eol and autoclrf.

I'd also like to know how to clean up based on rules like SA1507 - never more than one blank line in a row, and related rules to remove blank likes after { and before }

StyleCop is from Microsoft: https://github.com/DotNetAnalyzers/StyleCopAnalyzers

Using their own APIs, Roslyn Analyzers verifies certain conditions about the source code and, if necessary, feeds back into the compiler in the form of compilation warnings and errors. An example would be StyleCop.

StyleCop.Analyzers

- StyleCopAnalyzers but I wasn't able to find an official CLI tool?

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.

I've been using Neovim (on Windows, not WSL) with Unity and the Omnisharp LSP smoothly for a while now, and it's definitely possible to have a decent experience. Assuming your config is already setup for LSP, completion, snippets, etc., there are a few Unity/Omnisharp specific workarounds to be aware of:

I solved it using the workaround at the end of this issue thread in omnisharp-roslyn

See: https://github.com/OmniSharp/omnisharp-roslyn/issues/2483 for some solutions.

No, Sematic Tokens has an issue opened for it since Dec 2022, with couple (well, at least one that I have seen) PRs open trying to fix it and some hacking around the issue in the comments, but it's not solved afaik.

Have a Look at this

I think the issue is related to 'Semantic Tokens' introduced in version 0.9 https://github.com/OmniSharp/omnisharp-roslyn/issues/2483

I did, but it's a little bit tricky. If you could wait some hours I will share it with you after work. You can take a look at this thread first: https://github.com/OmniSharp/omnisharp-roslyn/issues/2250