roslynator

Add the analyzer package with dotnet add PROJECT.csproj package Roslynator.Analyzers. This enables build-enforced diagnostics, and you configure rule severity in the root .editorconfig using dotnet_diagnostic entries.

Install the CLI with dotnet tool install roslynator.dotnet.cli, then run roslynator find-unused on your solution or project. Build first so Roslynator has compiled context, and scope results with --projects or --include flags.

The NuGet analyzer packages provide the actual diagnostic rules enforced at build time. The CLI is a separate tool for explicit analyze, fix, format, and find-unused workflows; it does not supply the analyzer rules by itself.

Yes, but you must establish clear rule ownership in .editorconfig to avoid duplicate diagnostics. Disable overlapping Roslynator rules where StyleCop or SDK analyzers already cover the same checks.

Avoid it when the repo already has overlapping analyzer packs with no consolidation plan, or when formatting is already standardized on dotnet format or CSharpier and only formatting work is needed.

Use dotnet_diagnostic.RCSxxxx.severity entries set to none, suggestion, warning, or error. Roslynator also supports roslynator_ prefixed options for style behavior and roslynator_refactoring toggles for individual refactorings.