Getting Started with NDepend on Windows
- Either watch the 5 minutes video below...
- ... or read the tutorial with explanations and screenshots
- Once you got the product installed and running don't miss out the Walkthrough Videos and the Use Cases pages.
Getting started with NDepend (5mn)
Tutorial with explanations and screenshots
- Installing the NDepend extension for Visual Studio 2026, 2022, 2019, 2017, 2015, 2013, 2012 or 2010
- Analyzing a Visual Studio solution
- Analyzing a .NET applications using Visual NDepend
Installing the NDepend extension for Visual Studio 2026, 2022, 2019, 2017, 2015, 2013, 2012 or 2010
- Download the NDepend installation zip file
- To install NDepend, just unzip the files in a private application folder on your machine. Don't unzip files in '%ProgramFiles%\NDepend'. This might provoke problems because of Windows protection.
- If you are running NDepend Professional Version, just type your license key in the NDepend activation dialog to activate your machine.
- Start NDepend.VisualStudioExtension.Installer.exe
-
Click the button Install for the right Visual Studio version
- Start Visual Studio
Analyzing a Visual Studio solution
- Start Visual Studio after having installed the NDepend addin.
- Open the Visual Studio solution containing the code to analyze.
-
Click the greyed NDepend circle status (bottom right of the Visual Studio window)
OR
click the menu NDepend > Attach new NDepend project to current Visual Studio solution
-
Note:
- A NDepend project can be attached to several Visual Studio solutions.
- This is useful if you wish to analyze several .NET assemblies compiled with several Visual Studio solutions.
- A benefit will be the possibility to navigate across several Visual Studio solutions opened in several Visual Studio instances.
- The dialog opened proposes to create a new NDepend project (.ndproj file extension) that references the Visual Studio solution .sln file. This NDepend project file will be then referenced by the .sln file, this is how it is attached to it. By default projects containing test in their names are filtered out, they are not analyzed. If needed you can modify the filter(s). You can also reference more assemblies from the tab No assembly outside the VS solution will be analyzed.
- Click Ok : the NDepend analysis start. It will just take a few seconds to analyze your code base for the first time. If you let the Build Report check box checked, a report will be created and shown in a new browser window.
Analyzing a .NET applications using Visual NDepend
The NDepend Visual Studio extension has no impact on the Visual Studio process performances. However if you prefer you can use 100% of NDepend features outside Visual Studio thanks to the standalone executable VisualNDepend.exe. To do so:
- Start VisualNDepend.exe
-
Select one of the options:
- Analyze Visual Studio solutions and Visual Studio projects
- Analyze .NET assemblies in folder
- Analyze a set of .NET assemblies
- Click OK. It will trigger the analysis of your assemblies and code source by NDepend.Console.exe. This analysis will take a few seconds. Once done, the result is displayed in the VisualNDepend.exe UI.
Sample Reports
NDepend generates interactive web reports that provides valuable and detailed insights about your .NET code quality:
Reports of NDepend.AI Fix Runs
Eight runs on eight open-source code bases fixed by NDepend.AI driving Claude Code (Opus as the premium model, Sonnet as the economy model). Each report opens on its AI Assistant tab: the complete log of the run, from the planning pass to the fix rounds, the parallel agent sessions, the tests, the change review and the final report, next to the NDepend report of the fixed code, diffed against the code at the start of the run.
| Code base | Issues fixed | Duration | Cost | Coverage | Tests (+written) | Bugs found |
|---|---|---|---|---|---|---|
| eShopOnWeb | 468 / 493 95% | 1h 21min | $44 | 45% → 97.5% | +506 619 green | 3 |
| NopCommerce (large scale fix) | 3,711 / 3,781 98% | 5h 23min | $261 | 23% → 43.6% | +3,476 4,580 green | 8 |
| Jellyfin (large scale fix) | 1,514 / 1,644 92% | 11h 23min | $543 | 31% → 56.2% | +4,303 8,017 green | 17 |
| Flow Launcher (large scale fix) | 2,837 / 3,109 91% | 6h 17min | $294 | 11% → 60.8% | +2,744 3,236 green | 5 |
| Spectre.Console (large scale fix) | 967 / 1,071 90% | 1h 31min | $64 | 71% → 98.5% | +1,507 2,747 green | 7 |
| Microsoft.FeatureManagement | 283 / 292 97% | 1h 06min | $25 | 78% → 99.6% | +200 347 green | 1 |
| Carter | 222 / 223 99% | 39min | $13 | 68% → 99.6% | +107 271 green | 0 |
| NodaTime | 354 / 387 91% | 1h 26min | $48 | 98% → 99.4% | +313 23,029 green | 0 |
The figures are those of each report's final report:
- Issues fixed: the issues of the targeted set that NDepend's re-analysis finds fixed.
- Duration: the wall-clock duration of the run.
- Cost: the cost billed by the agent's provider.
- Coverage: the code coverage before and after the run.
- Tests (+written): the tests the run wrote and the tests green at the end.
- Bugs found: the potential bugs the agent reported in the application code while writing tests and fixing issues. The run leaves them unfixed and lists each one in its final report, to check by hand.
NDepend.AI Fix Runs with Eight Coding Agents
The same run on a small experiment code base TrainTrain, driving eight different coding agents: the same 22 issues to fix (architecture, naming, visibility, code coverage and a few issues to suppress on purpose), the same NDepend verification of every fix. Each report opens on its AI Assistant tab, with the complete log and the final report of the run.
| Coding agent | Issues fixed | Suppressed | Left on purpose | Still to fix | Duration | Cost | Coverage | Tests (+written) | Bugs found |
|---|---|---|---|---|---|---|---|---|---|
| Claude CodeOpus 5.5 / Sonnet 5.5 | 14 / 22 64% | 3 | 3 | 2 | 6min 35s | $1.65 | 69% → 77.4% | +7 29 green | 2 |
| Codexgpt-6.1-sol / gpt-6-luna | 13 / 22 59% | 4 | 3 | 2 | 5min 44s | ~$0.22 * | 69% → 77.2% | +7 29 green | 1 |
| GitHub Copilot CLIclaude-haiku-4.5 (its default) | 14 / 22 64% | 4 | 3 | 1 | 16min 38s | ~$1.63 * | 69% → 78.7% | +15 37 green | 0 |
| JunieOpus 5.5 / gemini-3.7-flash | 14 / 22 64% | 3 | 3 | 2 | 9min 10s | $2.11 | 69% → 77.2% | +6 28 green | 2 |
| Kiroclaude-sonnet-4.5 / claude-haiku-4.5 | 13 / 22 59% | 4 | 3 | 2 | 23min 28s | 18.8 credits | 69% → 77.2% | +12 34 green | 0 |
| Mistral Vibemistral-medium-3.5 / zai-glm-5-3-flash | 15 / 22 68% | 4 | 3 | 0 | 19min 52s | $2.98 | 69% → 79.2% | +15 37 green | 0 |
| Muse Codemuse-wonder-1.0 / muse-spark-1.3 | 13 / 22 59% | 4 | 3 | 2 | 12min 01s | $5.51 | 69% → 77.2% | +12 34 green | 0 |
| OpenCodeglm-5.3-flash-free | 13 / 22 59% | 4 | 3 | 2 | 39min 18s | $0 * | 69% → 89.4% | +17 39 green | 2 |
The figures are those of each report's final report:
- Coding agent: under its name, the premium model / the economy model of the run.
- Suppressed: the issues hidden by a SuppressMessage attribute the agent added, not fixed and left out of the fixed figures.
- Left on purpose: the issues the agent declined with a reason, a human decision. In all eight runs, the same 3 methods
left untested:
GetTrain(),BookSeats()andGetBookingReference()create their ownHttpClientand call a remote HTTP service, with no way to pass in a fake: they need an integration test, not a unit test. - Still to fix: the issues left, branches the tests found unreachable, dead code to delete by hand (for Kiro, 2 coverage issues not reached, to retry in another run).
- Cost: * Codex and Copilot CLI report no cost of their own: the run's tokens priced at the published rates (partial for Copilot CLI). Kiro bills in credits. OpenCode ran a free model.
Reports Compared with a Baseline (usual NDepend reporting, no AI)
For these sample reports are imported:
Such serverless report can be generated by invoking... NDepend.Console.exe $absolute-path-to-an-NDepend-project-file$...from your CI/CD running on Windows, Linux and Mac
You can generate the report using a trial license, a Build-Machine license |
|
Use Cases
NDepend is a feature rich product. To help you get started quickly you can refer to the use cases that best fulfill your needs: