The only issue with this is where you have multiple solutions and each has at least one shared project which has Nuget references. i.e.
Now consider these to be two seperate modules and my build server checks out the stuff it needs for Solution1 and Solution2 seperately, the shared repositories.config file is going to have references to the packages.config files for both ProjA and ProjB,
whereas when building Solution1, the Solution2 exclusive stuff won't be downloaded to the workspace...
Not sure if that makes sense...