-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document buildTransitive scenarios #13495
Comments
@rrelyea can we have this assigned? I can work with them to get it documented. |
Is this still undocumented? |
@nkolev92 any chance of getting this documented? :) |
@JonDouglas maybe this can part of the docs bash? |
Any updates on this? I think some more documentation on this would help me with my current situation. I'm writing a package (call it Library) that uses CsWinRT. For an app consuming my Library's nupkg, it needs certain CsWinRT dlls. Using targets and buildTransitive, I am able to get all dlls into the nupkg, and 4/5 dlls copied to the output directory of the consuming app. But one is failing to be found for copying, and I'm grinding through binlogs to figure it out. Any documentation/samples would be very helpful! |
Sorry no update until just reading this comment. We never got to this for the last couple doc bashes. If I understand this correctly, we want to document https://github.com/NuGet/Home/wiki/Allow-package--authors-to-define-build-assets-transitive-behavior There are a number of scenarios on the spec, but no actual examples. I'll look into it after the other p1 |
Thanks @JonDouglas. One question though is how much of the spec actually got implemented, and if there are any differences in behavior/syntax etc… Seems risky to create docs based on an original spec and not the actual implementation |
I have a related issue filed here: microsoft/ApplicationInsights-Profiler-AspNetCore#173. And I ran into 6091, which is closed but it is not very clear, is the feature actually implemented? And if it is, how to use it? |
Document the buildtransitive scenarios:
#6091
The text was updated successfully, but these errors were encountered: