We still list the top-level packages based on the package definitions within the .csproj file, but nested packages are discovered using the nuget-deps-tree package. That package parses the project.assets.json file. After doing some research, this seems like the easiest approach to provide a nested package tree for nuget packages. The project.assets.json file should exist for dotnet core projects.
This should be non-breaking, in that if the nuget-deps-tree package has any problems discovering nuget packages, then no nested package deps are displayed (but the top-level packages are still displayed).
Fixes #235
We still list the top-level packages based on the package definitions within the .csproj file, but nested packages are discovered using the
nuget-deps-tree
package. That package parses theproject.assets.json
file. After doing some research, this seems like the easiest approach to provide a nested package tree for nuget packages. Theproject.assets.json
file should exist for dotnet core projects.This should be non-breaking, in that if the
nuget-deps-tree
package has any problems discovering nuget packages, then no nested package deps are displayed (but the top-level packages are still displayed).https://user-images.githubusercontent.com/102141/208253522-8dc70204-328f-4afc-9799-28ad80c5838d.mov