I am seeing in the VS 2013 Preview that either through the Manage NuGet Packages Dialog or the Package Manager Console that my .nuget\nuget.config custom repository path is not being used and always goes into my $(SolutionDir)\packages folder. I am running the latest and greatest 2.6 Nuget VSIX and command line tools. I am not having this issue with VS 2012. Is this just a missing feature in the VS 2013 VSIX install compared to 2012?
Comments: So upon further testing I had another nuget.config get pulled in (hierarchical nuget.config) and the repositoryPath in there was invalid (as in wrong config element structure and wrong relative path). So my next test was to remove the hierarchical nuget.config all together, however my .nuget\nuget.config was still not using the custom repositoryPath. Finally I was able to get it working through my hierarchical nuget.config pointing to the correct relative path inside the correct xml configuration. It sure seems like the .nuget\nuget.config doesn't use the repositoryPath at all. Can we confirm this?
Comments: So upon further testing I had another nuget.config get pulled in (hierarchical nuget.config) and the repositoryPath in there was invalid (as in wrong config element structure and wrong relative path). So my next test was to remove the hierarchical nuget.config all together, however my .nuget\nuget.config was still not using the custom repositoryPath. Finally I was able to get it working through my hierarchical nuget.config pointing to the correct relative path inside the correct xml configuration. It sure seems like the .nuget\nuget.config doesn't use the repositoryPath at all. Can we confirm this?