Specify Nuget config to avoid accessing private NuGet repo #937
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks good to me. That build failure is one of our problem tests. We have a fix for that in another PR. |
|
Thanks for the comment. |
annymsMthd
added a commit
that referenced
this pull request
May 4, 2015
Specify Nuget config to avoid accessing private NuGet repo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I ran build.cmd, I encountered the shell asking for my id and password to access the corporate nuget repo. It's sensitive information and you wound't want to type in your passwords if you don't trust the script 100%.
It happened because NuGet.exe install used the default NuGet.Config in %appdata%\Nuget. By specifying the given nuget.config in \src.nuget, we can avoid this issue.