Skip to content
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

Open
nkolev92 opened this issue Jan 23, 2019 · 8 comments
Open

Document buildTransitive scenarios #13495

nkolev92 opened this issue Jan 23, 2019 · 8 comments
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Type:Docs

Comments

@nkolev92
Copy link
Member

Document the buildtransitive scenarios:

#6091

@karann-msft
Copy link
Contributor

@rrelyea can we have this assigned? I can work with them to get it documented.

@zkat zkat transferred this issue from NuGet/Home Apr 20, 2020
@ericsampson
Copy link

Is this still undocumented?

@ericsampson
Copy link

@nkolev92 any chance of getting this documented? :)

@nkolev92
Copy link
Member Author

cc @JonDouglas @aortiz-msft

@JonDouglas maybe this can part of the docs bash?

@j0shuams
Copy link

j0shuams commented Jan 6, 2021

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!

@JonDouglas
Copy link
Contributor

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 buildTransitive based on the spec:

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 doc-bash issue.

@ericsampson
Copy link

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

@xiaomi7732
Copy link

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?

@nkolev92 nkolev92 transferred this issue from NuGet/docs.microsoft.com-nuget Jun 1, 2024
@nkolev92 nkolev92 added Priority:1 High priority issues that must be resolved in the current sprint. Type:Docs and removed P1 labels Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Type:Docs
Projects
None yet
Development

No branches or pull requests

8 participants