Browse by term
A concrete Directory.Build.props example that incorporates Microsoft's .NET analyzers and StyleCop Analyzers, and applies stricter analysis to production projects than to tests and tooling.
How a cross-team rule set for .NET static code analysis splits responsibilities between Microsoft's analyzers and StyleCop, and why production and non-production code get deliberately different strictness levels.
Why applying one uniform static-analysis ruleset to both production and test code serves neither well, and what a more relaxed ruleset for tests actually buys a team.
Why brownfield and greenfield code call for different static-analysis rulesets, and how that split turns modernization into an incremental, sustainable process instead of a single risky migration.