Could the [command lines](http://docs.nuget.org/docs/reference/command-line-reference) be extended to include an explicit option for Continuous Integration servers to allow nuget package updates etc on build servers or build Agent PC's?
NuGet.exe -config -SET EnableNuGetPackageRestore=True
This would reduce the need to set environment variables or open up Visual Studio under a CI authenticated user to set the user specific setting on multiple build servers/agents.
Comments: Sorry about the slow response. I was looking at how to use Nuget command line option on CI servers ([http://www.finalbuilder.com/continua-ci.aspx](Vsoft - Continua)). Continua allows you to use a "farm" of CI server agents to process CI projects. __CI process under review__ In context, I don't always store the nuget\packages folder in Source control (decision might need reviewing). So the build of software on a CI server requires the nuget packages to be downloaded first. _Thoughts_ If the nuget package folder is not stored in the source code repository, could nuget command line be used to automatically download the required packages to the CI server. __CI Future process under review__ Say I have a corporate development framework used by 30 applications, how could I test compatibility of a major upgrade of functionality (including breaking changes) across all the software that used the previous framework via a CI server? I guess this is one of the issues with frameworks, is as they evolve and how to test and distribute upgrades to LOB frameworks. _Thoughts_ Could I use the CI server + Nuget command line to "test" a new version of the internal Nuget released package without having to branch all the code repositories and point at the "test" nuget package for the changed corporate framework?
NuGet.exe -config -SET EnableNuGetPackageRestore=True
This would reduce the need to set environment variables or open up Visual Studio under a CI authenticated user to set the user specific setting on multiple build servers/agents.
Comments: Sorry about the slow response. I was looking at how to use Nuget command line option on CI servers ([http://www.finalbuilder.com/continua-ci.aspx](Vsoft - Continua)). Continua allows you to use a "farm" of CI server agents to process CI projects. __CI process under review__ In context, I don't always store the nuget\packages folder in Source control (decision might need reviewing). So the build of software on a CI server requires the nuget packages to be downloaded first. _Thoughts_ If the nuget package folder is not stored in the source code repository, could nuget command line be used to automatically download the required packages to the CI server. __CI Future process under review__ Say I have a corporate development framework used by 30 applications, how could I test compatibility of a major upgrade of functionality (including breaking changes) across all the software that used the previous framework via a CI server? I guess this is one of the issues with frameworks, is as they evolve and how to test and distribute upgrades to LOB frameworks. _Thoughts_ Could I use the CI server + Nuget command line to "test" a new version of the internal Nuget released package without having to branch all the code repositories and point at the "test" nuget package for the changed corporate framework?