Skip to content
Source on GitHubVisitors

.NET dependency graph

Show the projects of a .NET solution, the NuGet packages they use and every reference between them.

Diagram · origin tag dotnet/dependency-graph · Infrastructure, network & cloud diagrams

Availability

Availability per host
HostStateHow to get it
StandalonePrototypeNot yet released
DesktopPrototypeNot yet released
IntelliJ PlatformNot plannedNot planned
Visual Studio CodeNot plannedNot planned
EclipseNot plannedNot planned
ThinkRailNot plannedNot planned
NotionNot plannedNot planned
ClaudeNot plannedNot planned

What it is for

.NET project and package dependency graph (read-only: the projects of a `.sln`/`.slnx`, the NuGet packages they consume, and every `ProjectReference` and `PackageReference` between them, computed from the project files rather than authored; the solution is never written, and node positions a user arranges are authored into the `.adp`); dotnet-dependency-graph

Why a specialized view helps

References are spread over many project files; one graph reveals cycles, duplicate packages and unexpected couplings.

File formats

Not described yet.

Screenshots

The four projects with their target frameworks on the left, the NuGet packages with their versions on the right, and the reference edges between them; Serilog outlined, showing the two versions referenced (3.1.1 and 4.4.0). Nothing selected.

Standalone, at 3e2df46

What is visible: The four projects with their target frameworks on the left, the NuGet packages with their versions on the right, and the reference edges between them; Serilog outlined, showing the two versions referenced (3.1.1 and 4.4.0). Nothing selected.

Why it matters: Projects, packages and every reference between them appear together, and a package referenced in two versions is outlined, which is exactly the kind of problem a list of project files hides.

Licence: Apache-2.0

Background

Focus areas

Sources