dotnet-inspect: relationships and dependency graphs

Use this skill to map how code connects: what implements or extends a type, what it depends on, and who calls it. Dependency graphs and Member Call Graphs share the same graph gestures: add --tree for a standalone path view, --mermaid for a standalone diagram, or --markdown --mermaid to embed one.

dnx dotnet-inspect -y -- <command>

With a positional type, scope relationship commands with --project path/to.csproj, repeatable --package Foo, --library path.dll, --platform, --extensions, --aspnetcore, and --tfm net9.0. Without a positional type, depends treats repeatable --package, --nuspec, --library, and --project options as explicit roots; exclusive --package-prefix PREFIX admits up to 500 package roots by default and can be bounded explicitly with --max-packages.