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

Support for linked content files #2895

Closed
MichaelKetting opened this issue Jun 3, 2016 · 2 comments
Closed

Support for linked content files #2895

MichaelKetting opened this issue Jun 3, 2016 · 2 comments
Milestone

Comments

@MichaelKetting
Copy link

I'd like to propose an extension to the content file feature introduced in NuGet v3.3.
http://blog.nuget.org/20160126/nuget-contentFiles-demystified.html

Linked Content Files

Right now, the content files are copied into project's source tree from the nuget package. This generates a lot of noise in the VCS when updating a nuget package, or, if the content files are bigger, e.g. a chm file or a cab-file containing an ActiveX control or some other executable, they also bloat your git repository.

It would be great to be able to avoid these issues by simply being able to add a link to the file instead of copying the file.

@davidmatson
Copy link

+1

I do this manually today by removing and re-adding as linked items from the packages folder, but it's a pain and would be really nice to add this support.

@emgarten
Copy link
Member

ContentFiles now use <Link> in nuget 4.0.0.

@emgarten emgarten added this to the 4.6 milestone Nov 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants