architecture-review

Detect layering violations and dependency cycles in a C# solution by loading the workspace into a Roslyn MCP server and running an architecture audit. The audit generates project- and namespace-graphs to surface improper references and structural breaches.

A Dependency Inversion Principle violation in C# architecture occurs when high-level modules directly depend on low-level modules instead of abstractions. The audit identifies these improper downward references and cross-layer leaks to enforce clean architectural boundaries.

Yes, you can scope an architecture audit to a specific project or namespace within a multi-project solution. This focuses the dependency graph analysis and cycle detection on targeted code areas rather than evaluating the entire solution graph.

Find cross-layer leaks and improper references using Roslyn by leveraging the MCP APIs to load workspaces and generate dependency graphs. The audit identifies symbol-level leaks and produces an evidence-backed report with file and line references.

The best way to audit a multi-project C# solution for clean architecture is running an automated analysis that checks for layering breaches, DIP violations, and composition root issues. This produces a prioritized report with actionable remediation guidance.

Yes, the architecture audit report includes file and line references for DIP violations. It produces a prioritized, evidence-backed report that traces symbol-level leaks and structural breaches directly to their source locations for actionable remediation.