You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: