We've been happily using nuget to retrieve 3rd party dependencies, and have just started to use Nuget to manage our own internal dependencies.
We've come across an issue where we want to install files into a projects content, but not add those files to the project. The issue is that when Content files are added at a path that is currently ignored by VS, it will attempt to add that ignored
path to the project. This can take a significant amount of time.
Is there a way to indicate that files should be installed, but only added to a project if the parent path is currently included?
Our package file has the following structure:
In our consuming VS project, we have this structure:
/our-content <- included in VS project
/directory/ <- excluded by VS project
As you might predict, when we add our nuget package, we end up with this:
/directory/ <- *included* by VS project
This addition recursively adds, to the project, all the files in the 3rd party directory. Takes upwards of an hour.
We'd love to be able to say to nuget, "Add these files to the filesystem, but don't add references to the project".