mcaf-dotnet-complexity

You can analyze .NET codebases for excessive cyclomatic complexity, low maintainability index, and high class coupling using built-in .NET analyzers. It targets repositories requiring complexity-driven refactoring gates and enforces rules like CA1502, CA1505, and CA1506.

You can enforce maintainability index limits in .NET by configuring maintainability thresholds using CodeMetricsConfig.txt and .editorconfig. This setup ensures code contributions meet your defined quality standards before merging.

Yes, you can integrate code complexity checks into a .NET CI pipeline using provided commands. This allows development teams to automatically prevent new code contributions from introducing overly complex logic that is difficult to maintain or test.

The .NET analyzer rules used to detect high class coupling and complexity include CA1501, CA1502, CA1505, and CA1506. These rules are enforced through .editorconfig and CodeMetricsConfig.txt to manage code coupling and maintainability.

No external dependencies are required for this code complexity analysis. It operates using built-in .NET analyzers to identify overly complex methods and excessive coupling directly within your .NET repositories.

Using built-in .NET analyzers for code refactoring gates provides direct enforcement of rules like CA1502 and CA1506 without external dependencies. It targets repositories requiring maintainability thresholds and complexity checks natively within the .NET ecosystem.