dotnet-roslynator

C# static analysis identifies code quality issues by installing Roslynator.Analyzers packages and running the Roslynator CLI to scan .NET repositories for actionable improvements. This extends coverage beyond default SDK analyzers to detect dead code and enforce broader rule sets.

Yes, you can auto-fix C# code issues using the Roslynator CLI fix command. The CLI workflow applies automated code corrections for detected analyzer violations, enabling batch processing of auto-fix workflows during local development or CI pipeline execution.

You configure C# analyzer rules by defining rule behavior and severity levels in an .editorconfig file. This EditorConfig-driven customization ensures Roslynator analysis adheres to specific team standards and integrates consistently across local development and CI environments.

The best way to detect unused code in a C# project is using the Roslynator CLI find-unused code command. This dead-code detection feature scans .NET repositories to locate and report unreachable code elements for safe removal.

Yes, Roslynator works alongside existing .NET SDK analyzers by providing broader static analysis and additional rule coverage. It extends default SDK capabilities with open-source analyzers, optional CLI workflows, and auto-fix features without replacing the built-in SDK tooling.

You integrate C# static analysis into a CI pipeline by configuring the Roslynator CLI to run analyze checks during the build process. EditorConfig files define the rule behavior, ensuring consistent code-quality gates and automated violation reporting across continuous integration environments.