Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support specifying path to Nuget.Config for NuGet settings on VS #7533

vsfeedback opened this issue Nov 21, 2018 · 3 comments


Copy link

@vsfeedback vsfeedback commented Nov 21, 2018

In a large, multi-solution environment, managing Nuget sources can be a problem, especially when repeated change is required in those sources. By default, when no solution is open, you edit your machine's nuget.config and when you edit your local folder's nuget.config. This can lead to dozens of nuget.config files existing that need to be found and updated when a change occurs.

it would be great to be able to specify a file path for the nuget.config to use for a solution.

It would be better if we could specify a source control path to use for nuget.config for the solution.

This issue has been moved from
VSTS ticketId: 731466

These are the original issue comments:

Fiona Niu[MSFT] on 11/18/2018, 08:22 PM (44 hours ago):

Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. You will hear from us in about a week on our next steps.

@anangaur anangaur changed the title Support specifying path for Nuget.Config Support specifying path to Nuget.Config for NuGet settings on VS Nov 21, 2018

This comment has been minimized.

Copy link

@anangaur anangaur commented Nov 21, 2018

Related epic issue: #7284


This comment has been minimized.

Copy link

@nkolev92 nkolev92 commented Nov 21, 2018

If a NuGet.Config is placed next to a solution file it already is treated as a solution level config.

Furthermore if you set the clear tag for all the elements you are effectively limiting the configuration to just that single file.
See for example.

Basically, you can already achieve most of this ask with the current state of the tooling.
The limitation is that you cannot edit that specific config from the VS UI.

I think this is something that should be taken into consideration when tackling #1820, which talks about the overall config experience rather than 1 specific scenario.

I think we can/should dupe this out to #1820 and add the feedback there.


This comment has been minimized.

Copy link

@rrelyea rrelyea commented Nov 28, 2019

Duping out to #1820

@rrelyea rrelyea closed this Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
5 participants
You can’t perform that action at this time.