dotnet-inspect

To diff .NET package versions and find breaking API changes, compare the old and new package surfaces to identify removed or modified members. This version diff capability helps confirm method signatures and locate replacement members before upgrading dependencies.

Yes, you can trace type relationships by finding extension methods, implementors, and dependency chains for a specific .NET type. This relationship tracing supports debugging and API design scenarios when you need to understand how a type is consumed or implemented.

The best way to explore .NET library types without source code is querying the compiled API surface for metadata, member signatures, and hierarchy tracing. This deterministic library analysis removes guesswork by returning type discovery and documentation lookup results directly.

Yes, .NET API inspection works for upgrade planning and dependency exploration by comparing version surfaces and reviewing metadata. You can confirm whether method signatures changed between versions and identify additive API changes before committing to a package upgrade.

Type discovery may miss members if the referenced assembly is not properly loaded or if extension methods reside in external NuGet packages not yet queried. Inspect the full dependency chain and include all relevant platform libraries to ensure complete member coverage.