You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When viewing the Dependencies tab for a .NET tool package on nuget.org, no dependencies are listed. For example:
This is a lie, since I can navigate to the *.csproj file and clearly see the dependencies. But, I shouldn't have to dive into the source to determine which dependencies exist.
Click the Dependencies tab and notice the message "This package has no dependencies"
Navigate to the source code and notice the 3 dependencies listed
Expected Behavior
The dependencies listed in the *.csproj file should be displayed on the Dependencies tab. In the case of dotnet-sqlcache, I'd expect to see these dependencies listed:
Microsoft.Data.SqlClient
Azure.Identity
System.Private.Uri
Screenshots
No response
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered:
Yes, this is a legitimate issue. The reason this is the case today is that NuGet.org only reads the <dependencies> node in the .nuspec to populate this tab. For tool packages, this metadata does not exist. We would need to either change the tool authoring to add this metadata in a new/existing way or glean dependencies from another artifact inside the package. More details are here in a closed, related issue: #8323 (comment)
Impact
It's more difficult to complete my work
Describe the bug
When viewing the Dependencies tab for a .NET tool package on nuget.org, no dependencies are listed. For example:
This is a lie, since I can navigate to the *.csproj file and clearly see the dependencies. But, I shouldn't have to dive into the source to determine which dependencies exist.
Repro Steps
Expected Behavior
The dependencies listed in the *.csproj file should be displayed on the Dependencies tab. In the case of dotnet-sqlcache, I'd expect to see these dependencies listed:
Screenshots
No response
Additional Context and logs
No response
The text was updated successfully, but these errors were encountered: