dotnet list package supports showing package dependencies declared in packages.config

[Racer396]

Hello.
I want to make solution verifier to nuget dependencies in C# app.

If we have projects whats compile to one folder, and
ProjectA -> PackageName 1.0.0
ProjectB -> PackageName 2.0.0
In output folder we get only one .dll, and its may to runtime exception when one of projects try use some method in PackageName with other project version. (Like ProjectB use PackageName 1.0.0)

I want to build full dependencies graph for all project in solution and verify it before build and run my program.
How can i do this?

I can manually parse .csproj for packets, and go to .nuspec of each packages, get dependencies, and build tree manually, with comparing nuspec framework dependencies and .csproj framework, but i think there is a more correct way.

[rrelyea]

Dotnet list package is a start. (Only works in packageref now—adding packages.config support soon)

[Racer396]

Dotnet list package is a start. (Only works in packageref now—adding packages.config support soon)

Thx.

1. How soon will be added .config support?
2. Are there other ways to do this? Or Nuget.Core and Nuget.Client doesn't support this features and only use dotnet list package?

[rrelyea]

We hope to ship dotnet list package support for packages.config as early as NuGet 5.2.
No other "built-in" was to do this yet.

[scharnyw]

Any update on this after 3 years? The inconsistency in tooling between PackageReference and packages.config is a still a big frustration after all these time

[notofug]

dotnet list with support for packages.config would be great in combo with #10852

even more so if C++ projects with nugets via packages.config also are allowed