Code Foresting: Automating Architecture Governance for .NET Teams
summary
Creates a small CI-driven engine (F# + PowerShell, exposed as Cake tasks) that parses NDepend XML and Roslyn semantic data, rejects commits, and auto-updates DocFX docs when architecture rules fail; separates brownfield into a 5–7 project new solution and scripts old-artifact moves to keep IDE fast; ships NDepend, Roslyn, DocFx, Cake & PowerShell integrations and 40–50 automated rules that surface illegal entity use and ownership conflicts, runs in CI but long-term ROI remains unverified.
AI-written summary · about
chapters (9)
- 0:00The architecture challenge
- 5:53Principles of governance
- 10:33Overcoming common traps
- 16:51Code as a forest
- 20:05Five pillars of automation
- 23:34Implementation strategies
- 29:03Tools for expressive code
- 37:18Automated documentation
- 43:29Lessons and closing
related talks
49mFrom Code Reviews to Code Rules
53mEnforce Coding Standards in .NET: Overcome Broken Window Syndrome
43mOvercoming Broken Window Syndrome Code Verification Techniques for NET Develop
53mTools and practices to help you deal with legacy code
52mBuilding Community-Driven Security Analysis for Your .NET Software Supply Chain
59mDeep Dive: DotNet and CF Pipeline
27mDX for 10x IaC: The Force Awakens
50mAutomate Yourself Out Of a Job With Roslyn