dotnet-inspect

Use the diff command with a version range, for example diff --package System.CommandLine@2.0.0-beta4.22272.1..2.0.3. Add --oneline for a triage summary, then run diff with -t TypeName for detailed breaking and additive changes on a specific type.

Run member TypeName --package PackageName --oneline to scan the API surface compactly. Omit --oneline to see full signatures with documentation, or use -m MethodName to filter specific members including constructors via -m .ctor.

Yes, the same commands work on local .dll and .nupkg files as on NuGet packages and platform libraries. Point the command at the local file instead of using --package to inspect its types, members, and metadata.

Use the extensions command to find extension methods and properties for a type, and implements to find concrete types implementing an interface or base class. Both accept scope flags like --platform, --aspnetcore, or --package to control the search scope.

Generic types need quotes and the <T> syntax, for example 'Option<T>'. Using <> resolves to the abstract base instead of the concrete generic, so constructors and generic members will not appear.