A Roslyn-based analyzer library for C# and VB that provides refactorings, code analysis, and diagnostics.
Code Cracker is a Roslyn-based analyzer library for C# and Visual Basic that provides automated code analysis, refactorings, and diagnostics. It helps developers identify and fix code issues, improve code quality, and enforce best practices directly within their IDE or build process.
C# and Visual Basic developers working in Visual Studio who want to improve code quality through automated analysis and refactoring, as well as teams seeking consistent coding standards across projects.
It offers a comprehensive set of community-driven analyzers and fixes built on Roslyn, is completely free and open-source, and integrates seamlessly into development workflows via NuGet packages or Visual Studio extensions.
An analyzer library for C# and VB that uses Roslyn to produce refactorings, code analysis, and other niceties.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built directly on Microsoft's Roslyn compiler platform, enabling precise, context-aware diagnostics and fixes, as evidenced by analyzers like CC0021 for nameof() operator usage that leverage deep code understanding.
Offers real-time analysis and one-click fixes in Visual Studio via extensions or NuGet packages, boosting developer productivity without leaving the editor, with support for configurable severity levels.
Analyzers run during builds and integrate with SonarQube via a plugin, enabling consistent code quality enforcement across team projects and continuous integration pipelines, as highlighted in the README.
A fully open-source project with active community contributions, providing a wide range of analyzers at no cost, underscored by detailed contribution guidelines and a philosophy of collaborative development.
Optimized primarily for Visual Studio; while NuGet packages might work elsewhere, the extension-based experience and full feature set are tied to VS, with no mention of official support for other IDEs like Rider.
As a community-driven project, updates for new C# versions or additional analyzers can lag behind commercial tools, and the README notes that core team maintenance depends on volunteer availability.
Managing analyzer rules across projects via NuGet or .editorconfig requires manual setup, and the README warns about potential conflicts or performance hits if not carefully integrated, especially in large solutions.