Package bootstrap in scenario where packages are not in source control

Dec 20, 2011 at 12:46 PM
Edited Dec 20, 2011 at 12:47 PM

Nuget 1.6 doesn't fully solve the package bootstrap problem in cases where someone is using an alternate package source.  If I go grab a project from source control and it uses an alternate package source, I must know what that package source is and configure it in Visual Studio before I can build.  It seems to me that this could be solved by stashing the package source information in the packages.config file.  This would allow nuget to pull from the correct sources even if they are not configured in VS.NET.

Dec 20, 2011 at 1:03 PM

You can edit the .nuget\nuget.targets file and change the <PackageSource> tag to have all you package sources.
Multiple sources must be delimited by ;