I have a large number of projects on the go and several solutions (which are subsets of the project pool). Sometimes it's nice to have .sln just for specific testing.
Problems:
NUGet is attached to each decision individually.
NUGet likes to find downloads in the packages folder from the folder in which .sln is located. This is not perfect. I have a library folder for this kind of thing (one for all projects in the pool). However, I am glad that the NUGET subfolder is disconnected from this area of the library.
I like the convenience of NUGet, but I'm not so sure about the big design decisions.
Possible answers:
One thought was to have .sln and .csproj only for NUGET, and then reference the packages as usual. You are losing some of the automation in this way.
we don’t add packages to the original control and say that we recreate the project from the original control, then nuget will load the same versions that it was required (randomly) ... and I don’t even know nuget works this way. This will require a high degree of trust in the nuget payload provider. Not a good idea.
But in NuGet 1.4, it was planned to make it integrated into NuGet. We will add a new function to restore any missing packages and packages folder based on the package.config file in each project when trying to create a project.
http://haacked.com/archive/2011/04/27/feedback-request-for-using-nuget-without-committing-packages.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3a%20haacked%20%28you% 27ve% 20been% 20HAACKED% 29
... , . , .