Overcoming Broken Window Syndrome Code Verification Techniques for NET Develop
summary
Focuses on enforcing project-specific architectural rules rather than general linters and demonstrates five concrete approaches: ArchUnitNET style architecture unit tests that fail CI, a custom CLI using Metal Lama workspaces to query compiled assemblies, Roslyn analyzers for IDE squiggles and compile warnings, Metal Lama attributes/fabrics for compile‑time checks and codegen, and NDepend for dependency graphs and cyclic detection. Shows examples (factory naming, namespace dependency, IDocument placement), CI integration via GitHub Actions, baseline strategy to start quality from today, and tradeoffs between complexity and real‑time feedback.
AI-written summary · about
chapters (11)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:23Introduction: Code Quality and Broken Windows Syndrome
- 4:10Understanding Architecture Erosion in Software Projects
- 9:00Tools for Detecting Architecture Erosion and Violations
- 15:30Using Architecture Unit Tests for Code Verification
- 19:00Code Example: Implementing Architecture Unit Tests
- 24:00Tools to Manage Warnings in Your Codebase
- 30:15Introduction to Metal Lama and Code Verification
- 34:00Using Roslin Analyzers for Real-Time Code Quality Checks
- 40:00Managing Code Quality in CI/CD with Sonar and Kodana
- 42:30Conclusion: Effective Strategies for Code Quality Management
related talks
53mEnforce Coding Standards in .NET: Overcome Broken Window Syndrome
53mTools and practices to help you deal with legacy code
50mAnalyzing Code in .NET
53mCode Foresting: Automating Architecture Governance for .NET Teams
59mTechniques for writing high-quality code
54mContinuous Integration: Live Static Analysis using Visual Studio & the Roslyn API
20mSupporting your architecture with code coverage and static analysis rules
43mBuild in Quality