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 we analyze the transitive nuget dependencies of a solution, we get a list like the example below. Is there a way to generate such a list of all transitive dependencies recursively for the solution but by excluding all the packages that come from (are part of) the .NET Runtime and .NET SDK?
Use cases:
We want to generate a report for our customers what external nuget packages our proprietary framework depends on. But we don't want to list the indiviual .NET Runtime, BCL, SDK nuget packages individually, we just want to say "we depend on .NET 8".
In the context of SBOM security analysis we would like to have the general .NET CPE as our dependency.
We are maintaining our own in-house "approved" nuget feed that contains only a small subset of nuget.org. It is not allowed to release anything that contains nuget packages that are not part of this feed and hence nuget.org cannot be used as package source directly. Now we want to add all of the .NET BCL, Runtime, SDK packages to that feed, whenever a new version of .NET is released. But how do we find them?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When we analyze the transitive nuget dependencies of a solution, we get a list like the example below. Is there a way to generate such a list of all transitive dependencies recursively for the solution but by excluding all the packages that come from (are part of) the .NET Runtime and .NET SDK?
Use cases:
Beta Was this translation helpful? Give feedback.
All reactions