-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
dotnet restore does not try all sources for restoring #7906
Comments
@alaatm How did you resolve this? |
@NickDarvey Turns out there was no problem with the tools. The feed's password must be either in clear text format or if you need encrypted then it must be generated on the machine that will execute the restore. |
Alrighty, thank you @alaatm |
Has anyone seen a resolution or workaround when using a docker container for builds? |
Just in case anyone else ever finds this error via Google. We encountered this error because someone had missed a trailing forward slash from one of our NuGet feed URLs (hosted on ProGet) making it an invalid URL. |
Steps to reproduce
1-Create a project that references packages from public nuget, some myget feed and a private feed that requires authentication.
2-Add Nuget.config
Note that the
auth
feed uses version 2.3-Run the following
dotnet restore --configfile NuGet.config
Expected behavior
Packages are restored.
Actual behavior
dotnet restore tries to use only the
auth
feed to restore packages that reside in public nuget/myget.Environment data
dotnet --info
output: 1.0.0I should add that this error does not happen on my local machine, in fact it runs just fine. It only happens on VSTS, I use the dotnet-install.ps1 script to install 1.0.0 as following:
dotnet-install.ps1 -version "$(SdkVersion)" -installDir $(SdkPath) -Architecture x64
where:
SdkVersion=1.0.0
SdkPath=C:\dotnet-sdk
Am I doing something wrong here..?
The text was updated successfully, but these errors were encountered: