Skip to content

Conversation

@redging-very-well
Copy link

Adds a new NuGet.Config section which includes the otherwise undocumented behaviour of dotnet restore with the globalPackagesFolder setting.

This is an alternative to users who rely upon the previous repositoryPath behaviour.

Title

On the title describe
what you've fixed (or created) with this Pull Request (PR).

Summary

Insert a short (one or two sentence) summary here.

Fixes #Issue_Number

Note: The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.
Remove that line if you don't have issues associated with this
PR. Click on the Guidelines for Contributing link above for details.

Details

Explain your changes, and why you made them. If that
information is already available in the issue referenced
above, just referencing the issue is preferred to copying
the text.

This may not be necessary depending on the scope of the PR
changes. For example, "fix typo in introduction.md" is
sufficient to describe that PR.

Suggested Reviewers

If you know who should review this, use '@' to request a review.

Adds a new NuGet.Config section which includes the otherwise undocumented behaviour of dotnet restore with the globalPackagesFolder setting.

This is an alternative to users who rely upon the previous repositoryPath behaviour.
@dnfclas
Copy link

dnfclas commented Mar 14, 2017

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@guardrex
Copy link
Contributor

@Redgwell Thank you for pointing this out! The dotnet restore command doc probably isn't the best spot for this, as the command doc should probably only cover its direct usage. A link to it here would be nice once it finds a home. I've moved this to an issue for further discussion. If there's good spot for it, you can submit the PR on it, but let's see if we can find where this goes. Moved to #1730

@guardrex guardrex closed this Mar 14, 2017
@redging-very-well
Copy link
Author

Thanks @guardrex - I wasn't 100% sure that this was an appropriate place for this, so thanks for moving it over. I'll track the issue you've raised.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants