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

Pack should exclude items from targets/props files coming from packages #3927

Closed
emgarten opened this issue Nov 11, 2016 · 6 comments
Closed
Assignees
Milestone

Comments

@emgarten
Copy link
Member

Pack should exclude content items and other items declared in props/targets coming from dependency packages.

Currently this can be done by setting ExcludeRestorePackageImports=true

Steps

  1. Install a package that contains a targets/props file with content items
  2. Pack the project

Expected

Content items from the package will not be included

Actual

Content items from the package are included

@aL3891
Copy link

aL3891 commented Nov 26, 2016

I open an issue for this, #4013 but I figured i'd add a note here as well, is it really necessary to also set this to true when doing a restore as well? doing that blocks a really interesting scenario for me :)

@rrelyea
Copy link
Contributor

rrelyea commented Jan 6, 2017

please investigate, and let's have an impact/timeframe discussion.

@dasMulli
Copy link

Note that having props/targets that contribute build logic might be vital for pack to work as expected.
First example would be packages that contain logic to calculate assembly & package version like GitVersion (though this currently does not work for package references).
Other uses would be code and content generation logic.

@rohit21agrawal
Copy link
Contributor

rohit21agrawal commented Aug 16, 2017

@dasMulli calculating package version happens in the outer build, and this change wouldn't impact that. if you have a scenario that you are afraid might break, i'd really appreciate if you could test out some private bits. if you can, let me know and i will share them with you.

also tagging @AArnott @onovotny in case they are interested to try it out before i check this in.

@AArnott
Copy link
Contributor

AArnott commented Aug 16, 2017

Thanks. I am concerned both with the goal and how it is implemented. Both concerns are on the PR.

@emgarten
Copy link
Member Author

Closing based on the PR feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants