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

dependency groups #1544

zivkan opened this issue Jul 17, 2019 — with · 2 comments


Copy link

commented Jul 17, 2019 — with

This page should also document how to create a different dependency group for each TFM. The info already exists in the nuspec reference, but should also be here since it's so important and related to multitargeting packages.

Document details

Do not edit this section. It is required for ➟ GitHub issue linking.


This comment has been minimized.

Copy link

commented Aug 14, 2019

@zivkan To avoid duplicating content, it might be best to either put this content inside of an INCLUDE or create a new section and just link to the sub-section in the .nuspec doc. Should this new section in multi-targeting doc be called "Grouping assemblies by TFM"?

This comment has been minimized.

Copy link
Member Author

commented Aug 14, 2019 — with

Technically most of the information on this page is duplicated elsewhere, but here it's focused on a specific scenario rather than listing all the features. Avoiding duplication is good, but simply linking to other docs, I worry that it will increase the barrier for customers to understand quickly how to achieve what they want.

Anyway, if adding a new section on this page, I think "Declaring dependencies" is a good name. In the context of a package, when someone says assemblies, I think of the files in the lib/ or ref/, or runtimes/<rid>/lib/ folders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.