NDepend

Run NDepend on the legacy solution.

Use the Dependency Matrix to find the most 'tangled' assemblies.

Query for 'Dead Code' using CQLinq to remove unused methods.

Apply the 'Level' metric to identify the correct order for refactoring to .NET 8/9.

Integrate NDepend into GitHub Actions.

Set the baseline to the 'main' branch.

Execute analysis on the feature branch PR.

Fail the build if the 'Technical Debt' increased by more than 1 hour.

Run NDepend on the entire repository.

Generate the 'Technical Debt' report to estimate hidden costs.

Check for third-party library vulnerabilities and license compliance.

Analyze 'Architecture Health' to assess future maintainability.

Define a 'Layering' rule in CQLinq (e.g., 'Data layer cannot call UI').

Enable the rule in the Visual Studio extension.

As developers write code, NDepend highlights violations in real-time.

Visual Studio build is blocked until the circular reference is resolved.

Import dotCover or OpenCover XML files into NDepend.

Use the 'Complexity vs Coverage' graph.

Identify 'High Complexity' methods with 'Zero Coverage'.

Prioritize writing tests for those specific methods to maximize risk reduction.

Create a custom CQLinq rule for naming conventions.

Apply the rule globally across the solution.

Generate a report of all non-compliant members.

Bulk-fix issues using Visual Studio refactoring tools based on the NDepend list.

Configure Trend Charts on the Azure DevOps dashboard.

Monitor the 'Debt Ratio' percentage over several months.

Identify 'Metric Spikes' correlated with specific releases.

Allocate 'Refactoring Sprints' when debt exceeds a specific threshold.