Check the contents of the two user-level config files and keep the one you want under ~/.nuget/NuGet folder. If the tooling you use involves both locations, consider consolidating them by following these steps to allow you to work with only one user-level config file: Visual Studio 2022 for Mac (and later versions), only when working on classic Mono projects. Visual Studio 2019 for Mac (and earlier versions). These other tools look for the user config file under the ~/.config/NuGet folder: Majority of users use tools that look for the user config file under the ~/.nuget/NuGet folder. On Mac/Linux, the user config file location varies by tooling. On Mac/Linux, the user-level config file location varies by tooling On Mac/Linux, the user config file location varies by tooling.NET CLI uses ~/.nuget/NuGet folder, while Mono uses ~/.config/NuGet folder. Settings apply to all operations on the computer, but are overridden by any user- or solution-level settings. If $XDG_DATA_HOME is null or empty, ~/.local/share or /usr/local/share will be used (varies by OS distribution) Windows: %ProgramFiles(x86)%\NuGet\Config Mac/Linux: $XDG_DATA_HOME. Settings apply to all operations, but are overridden by any solution-level settings. Windows: %appdata%\NuGet\config\*.Config Mac/Linux: ~/.config/NuGet/config/*.config or ~/.nuget/config/*.config These configs cannot be edited by the tooling. Windows: %appdata%\NuGet\NuGet.Config Mac/Linux: ~/.config/NuGet/NuGet.Config or ~/.nuget/NuGet/NuGet.Config (varies by tooling) Additional configs are supported on all platforms. When restoring a project on the command line, the project's directory is treated as the solution directory, which can lead to differences in behaviour when restoring the project vs solution. 
Note that if a config file is placed in a project folder, it has no effect on that project. In a solution folder, settings apply to all projects in subfolders.
Config file locations and uses ScopeĬurrent folder (aka Solution folder) or any folder up to the drive root. Settings apply to all commands issued in the CLI, the Package Manager Console, and the Package Manager UI. A global NuGetDefaults.Config file also specifically configures package sources. NuGet's behavior is driven by the accumulated settings in one or more NuGet.Config (XML) files that can exist at solution- (project if no solution is used), user-, and computer-wide levels.
0 kommentar(er)
