Ideas about NuGet Hierarchical Setting
Pages 155
Home
Contributing
Specs
Incubation
Reviewing
- Centrally-managing-NuGet-package-versions
- Package Applicability
- dotnet list package --vulnerable
- Machine-readable output for dotnet list package
- Support Package Renames
- Advanced Search on NuGet.org
Reviewed
Implemented
- Enhanced package upload workflow
- Register package signing certificates
- Organizations on NuGet.org
- 2 Factor Auth for NuGet.org sign in
- Add nuget sources command to the dotnet CLI
- Author Package Signing
- Backporting PC to msbuild restore
- Deprecate packages
- Dotnet list package
- Enable repeatable package restore using lock file
- NuGet Client Package Debugging
- NuGet Package Debugging & Symbols Improvements
- NuGet Package Identity Verification
- NuGet Package Signing Client Policy
- NuGet Sign Command
- NuGet Verify Command
- Storing trusted repository
- Package Signatures Technical Details
- Package signing
- Packages.config SHA Validation
- Packaging Icon, License and Documentation within the nupkg
- Repository Signatures and Countersignatures Technical Specification
- Repository Signatures
- Show outdated packages
- Symbols Package Upload and Delete Workflow
Templates
Clone this wiki locally
There are several issues in current configuration settings.
-
NuGet setting dialog does not reflect hierarchical NuGet.Config. Currently, it’s confusing about where a package source comes from, where a package source goes to during adding new source. We should come up a new UI that makes user can modify each NuGet.Config on UI.
-
Currently there is no way to add username/password for each source on UI, user always need to use nuget.exe to add them, and also need to reopen the current solution to make the new setting take effect.
-
"clear" tag and NuGet.config priority are really confusing on Setting UI. Current setting UI doesn’t reflect which NuGet.Config contain “clear” tag and priority for each NuGet.Config. For example, user clone a solution from github and open it in VS, if there is a NuGet.config in this solution and it contains "clear" tag. Then when user open configuration setting, his global sources are missing, he will have no idea what happens unless he understands the "clear" tag thing.
We should address those issues in new configuration setting.
On the new configuration setting, it should have following feature:
-
Dialog window for each NuGet.Config, user can add and remove package source for each NuGet.config there.
-
Credential setting for each package source, user can add username and password for each source.
-
On each NuGet.config window, it should show information about clear tag, NuGet.config location and priority for current NuGet.config.
Discussion bug for NuGet Hierarchical Setting : https://github.com/NuGet/Home/issues/1820