dotnet restore --source is lacking Username/Password/ClearTextPassword support
See original GitHub issueSteps to reproduce
try to add a username/ClearTextPassword in the dotnet restore --source command
Expected behavior
My nuget repository requires authentication and it is not possible to add a username/ClearTextPassword in the dotnet restore command for a source
Actual behavior
It’s not possible to add a username/ClearTextPassword for a …source
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-preview2-1-003177)
Product Information: Version: 1.0.0-preview2-1-003177 Commit SHA-1 hash: a2df9c2576
Runtime Environment: OS Name: Windows OS Version: 10.0.14393 OS Platform: Windows RID: win10-x64
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
dotnet restore --source is lacking Username/Password ...
Steps to reproduce try to add a username/ClearTextPassword in the dotnet restore --source command Expected behavior My nuget repository ...
Read more >asp.net core - dotnet restore fails from Docker container
I ran into a similar problem with dotnet restore causing the Unable to load the service index for source https://api.nuget.org/v3/index.json ...
Read more >dotnet restore command - .NET CLI
Learn how to restore dependencies and project-specific tools with the dotnet restore command.
Read more >Troubleshooting NuGet Package Restore in Visual Studio
A description of common NuGet restore errors in Visual Studio and how to troubleshoot them.
Read more >NuGet Package Restore
During restore, NuGet ignores the order of package sources, and uses the package from the first source that responds to requests. If restore...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Workaround: use a NuGet.Config file with your custom feed.
Patch it during your CI build with a powershell script.
Then run
dotnet restore --config NuGet.Config
I went ahead and moved this to nuget/home#4126. Closing out the CLI copy.