We use latest nuget in VS2010/2012 for referencing dependencies such as Castle Windsor, Rhinomocks, AutoMapper, etc..
After nuget does its magic, the cs project file for project Acme might have a new reference item like this.
This works great for when project Acme is built in context of Solution Foo (where the Nuget dependency was originally established) but when project Acme is built in context of Solution Bar this breaks (we have package restore enabled for each solution).
Because we share projects across numerous solutions, Nuget dependencies are a source of pain. To make this work across all solutions, we change the hint path so it is relative to solution dir macro.
This works but requires alot of extra effort. Is there a better way to handle this scenario?