First, I'm trying to approach this from a Maven-like mindset, where I didn't need to be concerned where or how my dependencies were stored locally. It just worked.<br /><br />What I want to do is configure one packages folder for every single solution / project I have, rather than one for each solution. I'm aware that in 2.1 I can change the location of the packages folder to somewhere else in the file system. However, NuGet still adds references into the project using a relative path. Therefore, if I checkout the project into a folder that is at a different folder depth, I must now reinstall all of the packages to correct the HintPaths. <br /><br />Could an option be added to NuGet.config to make HintPaths absolute rather than absolute? I found a workaround to get an absolute path, but it's not the cleanest:<br /> <add key="repositoryPath" value="\\localhost\C$\packages" /><br /><br />I would also think that if NuGet was set up for a single package store, then packages should not be removed if uninstalled from a project, and that the repositories.config should not refer to the packages.config of any projects/solutions.<br /><br />Being able to configure this through the Visual Studio options would be a bonus.
Comments: Yes, if the hint paths were done away with altogether, I think that would work.
Comments: Yes, if the hint paths were done away with altogether, I think that would work.