On a similar note. So there is a packages folder that is maintained at the solution level and each project references the binaries under it. How do we handle updates? Why doesn't NuGet look at this packages folder before going off and obtaining
packages from the internet?
Case in point. I have several projects that all reference Rx-Core package version 1.0.2838.0. Well a few days ago Microsoft released Rx-Core version 1.0.2856.0. When I went to add the package to a new project I had created, Nuget proceeded
to download the 1.0.2856 version. However since the build deploys with the 1.0.2838 version, at runtime it threw an error about the wrong version.
I found Nuget just got in the way here, as if I just had a binaries folder and i went to reference the assembly I'd immediately get the version I had there and i wouldn't have to worry about something automatically upgrading me. I don't mind being
notified of updates, I don't mind updates in general, but i want to know about them... and they need to be referenced to every project in the solution not just one.
The way to go back and reference the already downloaded preexisting older version of this assembly was non-intuitive. I eventually found two ways of accomplishing this, but neither is particularly great.
First way was to drop down to the package manager console and add the package using a install-package with the -source folder option.
The second way was to go into the Nuget Package Manager settings within VS.NET and set our packages folder as an available package source.
It seems to me that the Nuget UI should first look in your packages folder to see what you already have. I know in 1.1 you added this recent packages, and that might be great for someone who through there day builds dozens of solutions, but for most
developers you work in one solution and you are modifying projects.
Or am I missing something?