Don't warn when the user doesn't provide a nuget.config #2878
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
jmyersmsft
approved these changes
Oct 25, 2016
|
|
Issue #2868 Leaving a log here since users that are on old nuget AND don't give a config can't auth to VSTS. Alternative would be parsing the nuget.config but due to varying nuget rules across version we don't want to get into parsing and understanding configs at this point (especially with the future being the credentialProvider flow where nuget continues to own the nuget.config discovery and parsing)
zjrunner
force-pushed
the
users/zackrun/2868-belownuget31
branch
from
6a99562 to
b6ebc00
Compare
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.
Issue #2868
Leaving a log here since users that are on old nuget AND don't give a config can't auth to VSTS.
Alternative would be parsing the nuget.config but due to varying nuget rules across version we don't want
to get into parsing and understanding configs at this point (especially with the future being the
credentialProvider flow where nuget continues to own the nuget.config discovery and parsing)