Execute the following script using your MyGet [feedUrl] and MyGet [username] , [password] and [apikey]. Run this from a commandline where you have access to nuget.exe (or set the path to your nuget.exe in a system environment variable).
nuget setapikey [apikey] -source [feedUrl]
nuget sources add|update -Name [name] -source [feedUrl] -User [username] -pass [password]
nuget setapikey [apikey] -source [feedUrl] -configFile [configFilePath]
nuget sources add|update -Name [name] -source [feedUrl] -User [username] -pass [password] -configFile [configFilePath]
Don't bother putting the above nuget.config files into source control as they'll only work on the machine and the account that created the configs.
To be able to share credentials, use the -StorePasswordInClearText option:
nuget setapikey [apikey] -source [feedUrl] -configFile [configFilePath]
nuget sources add|update -Name [name] -source [feedUrl] -User [username] -pass [password] -configFile [configFilePath] -StorePasswordInClearText
I'm trying this solution to work around the bug in TeamCity/Nuget around the authenticated feed but it still doesn't seem to be working. What is the right directory to put the nuget.config file in? Is it case sensitive (NuGet.config vs nuget.config)? does the source URL need to match the "internal"/localhost url of the feed? trailing / or no trailing /?
so many questions!