NuGet and multiple solutions
We have two solutions:  foo.sln and bar.sln

I have a common library that is used by both foo and bar. Common.csproj is used by both.

If I open foo and update nuget references, all references in Common.csproj point to foo/packages/.  If I later open bar and update nuget references, all references get set to those in bar/packages/.  Naturally, this pisses off the foo team as it can cause incompatibilities between Common.csproj and Foo-specific stuff like Foo.Data.csproj, which still points to foo/packages.


There must be some obvious solution other than: "create a huge solution that contains all your projects, and if you need to touch nuget, only do it from that solution."  

There seems to be an [issue on codeplex][1], (the top voted issue, incidentally), but evidently I'm too thick to understand how this issue is resolved.  Can someone explain how to fix this? 


  [1]: http://nuget.codeplex.com/workitem/215
NuGet and multiple solutions
===

We have two solutions:  foo.sln and bar.sln

I have a common library that is used by both foo and bar. Common.csproj is used by both.

If I open foo and update nuget references, all references in Common.csproj point to foo/packages/.  If I later open bar and update nuget references, all references get set to those in bar/packages/.  Naturally, this pisses off the foo team as it can cause incompatibilities between Common.csproj and Foo-specific stuff like Foo.Data.csproj, which still points to foo/packages.


There must be some obvious solution other than: "create a huge solution that contains all your projects, and if you need to touch nuget, only do it from that solution."  

There seems to be an [issue on codeplex][1], (the top voted issue, incidentally), but evidently I'm too thick to understand how this issue is resolved.  Can someone explain how to fix this? 


  [1]: http://nuget.codeplex.com/workitem/215