NuGet Product(s) Affected
Visual Studio Package Management UI
Current Behavior
Questions come up frequently about how Visual Studio evaluates the NuGet.Config file hierarchy—particularly in scenarios involving multiple config files and elements—and how that hierarchy maps to the NuGet settings surfaced in Visual Studio Options.
Today, it is not always clear from the VS Options UX:
- Which NuGet.Config files are currently in scope for a given settings page
- How those files are layered and merged
- How tags affect the effective settings users see or modify
This lack of visibility can lead to confusion when troubleshooting package sources, mappings, or other NuGet behaviors, especially when solution-, user-, and machine-level configs interact.
While the "Configuration Files" settings is useful in seeing the file hierarchy, it requires opening each file and inspecting them, in the right order, to understand how settings are being read and written for that repo.
Desired Behavior
Explore UX improvements that make it clearer—per Options page—which NuGet.Config files are in play and how precedence is applied (e.g., explicit file list, precedence indicators, or inline guidance).
Identifying when a <clear /> is or is not in play is one approach to consider.
Additional Context
No response
NuGet Product(s) Affected
Visual Studio Package Management UI
Current Behavior
Questions come up frequently about how Visual Studio evaluates the NuGet.Config file hierarchy—particularly in scenarios involving multiple config files and elements—and how that hierarchy maps to the NuGet settings surfaced in Visual Studio Options.
Today, it is not always clear from the VS Options UX:
This lack of visibility can lead to confusion when troubleshooting package sources, mappings, or other NuGet behaviors, especially when solution-, user-, and machine-level configs interact.
While the "Configuration Files" settings is useful in seeing the file hierarchy, it requires opening each file and inspecting them, in the right order, to understand how settings are being read and written for that repo.
Desired Behavior
Explore UX improvements that make it clearer—per Options page—which NuGet.Config files are in play and how precedence is applied (e.g., explicit file list, precedence indicators, or inline guidance).
Identifying when a
<clear />is or is not in play is one approach to consider.Additional Context
No response