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
There is currently no way of stopping the transitivity, however. You'd have to manually add each dependency and set Pack=false on it to stop this behavior.
We should support a new PackTransitive=false attribute to opt-out of this behavior. I'd still keep the transitive packing on by default since that's the most common approach when doing private assets for a dependency (in my experience, i.e. tools or msbuild tasks).
The text was updated successfully, but these errors were encountered:
Sometimes it may be useful to just pack the top-level dependency from a reference (i.e. you're getting the other deps by some other means, or the environment they run on doesn't require them, such as for Microsoft.Build.Framework, say).
This allows just setting PackTransitive=false to stop the transitivity.
Fixes#37
Currently, you can pack an entire graph of transitive dependencies along with your package by simply adding
PrivateAssets=all
on thePackageReference
:There is currently no way of stopping the transitivity, however. You'd have to manually add each dependency and set
Pack=false
on it to stop this behavior.We should support a new
PackTransitive=false
attribute to opt-out of this behavior. I'd still keep the transitive packing on by default since that's the most common approach when doing private assets for a dependency (in my experience, i.e. tools or msbuild tasks).The text was updated successfully, but these errors were encountered: