Generate Path Property for NuGet Package Dependencies? #11508
Replies: 3 comments
-
|
Why not suggest package consumers to reference your package dependence directly ? |
Beta Was this translation helpful? Give feedback.
-
|
Because then it's up to the user to retrieve two NuGet packages and also set the appropriate GeneratePathProperty on the second NuGet. The idea is to create one "seamless" experience for developers. This approach isn't intuitive but it seems to be about the only option. |
Beta Was this translation helpful? Give feedback.
-
|
I'm looking for a similar feature (not to copy contents from the 3rd party package but to access some of its build targets from my own build target). Is it possible to get the path to the transitive dependency without forcing the end-user to consume the transitive dependency explicitly? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I hope this post is in the right place.
Is it possible to get the Generated Path Property for a NuGet Package dependency?
I've created a NuGet package that depends on a third-party package that I want copied into my Project's directory .
The third-party NuGet package has not enabled copying to the output directory using the PackageReference style (works correctly using packages.config) and so the content ends up in the global packages directory.
I've added a .targets file to my NuGet package distribution in /build that copies the contents from the global location using the $(PkgNuGetName) variable, but this variable is empty because the GeneratePathProperty for this dependency is disabled I assume.
Please let me know if anything isn't clear or you need additional information!
Thanks for your time,
Levie
Beta Was this translation helpful? Give feedback.
All reactions