We work in an environment where it is not uncommon for developers to setup local repositories within their workspaces as they test and evaluate various alpha packages. More often than not their nuget.configs gets checked along with their code changes which breaks our CI builds. Worse when such builds get submitted to golden build servers it creates more problems since either the build would break there or if the developer used a repository which was visible to the golden build server, the alpha packages would be included in the golden builds.

Is there a way to put in an override that forces NuGet to ignore any config file other than the one in %appdata%? We work on TFS 2010 and VS 2010/2012 environment and can modify the default build workflows to put in any customizations that might be required during the build process.

Hello Nik,

Thank you for the suggestion.  I've created a new work item (http://nuget.codeplex.com/workitem/2969) based on your request.

HTH,
Clay

why not set up hierarchal configs on your build server and remove all unsupported sources?

Eddie not sure what you mean. As I said developers accidentally check in these files which propagate down to build servers as parts of CI builds. Since the whole process is dynamic, don't think I can do anything to prevent this really.