Enforce Coding Standards in .NET: Overcome Broken Window Syndrome
summary
Practical roadmap: enforce project‑specific rules with ArcUnitTest and Roslyn analyzers (reflect/Mono or Roslyn semantic hooks), or run a custom CLI using the Metal workspace to emit clickable warnings; spot architecture issues with NDepend (it shows cyclic dependencies) and manage thousands of legacy findings with Qodana baselines and quality gates. Metalama gives real‑time, attribute‑oriented validation and codegen (free tier available). Teams use three strategies: zero‑warning CI, baseline to ignore 15,000 warnings, or quality gates.
AI-written summary · about
chapters (9)
- 0:00Broken window syndrome in .NET
- 2:12Architecture erosion in long-term projects
- 9:06Tools for architectural defects
- 19:12Roslyn analyzers for validation
- 25:37NDepend for architecture assessment
- 28:48Metalama for real-time validation
- 33:57Managing existing warnings
- 44:38Code quality strategies
- 45:47Q&A
related talks
43mOvercoming Broken Window Syndrome Code Verification Techniques for NET Develop
50mAnalyzing Code in .NET
49mFrom Code Reviews to Code Rules
53mCode Foresting: Automating Architecture Governance for .NET Teams
53mTools and practices to help you deal with legacy code
54mContinuous Integration: Live Static Analysis using Visual Studio & the Roslyn API
44mClean as You Code Your Projects
01h 01mBuilding Code Analyzers with the new C# compiler platform (Roslyn)