You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run the "dotnet tool install" or "dotnet tool update" command line in a folder that contains a nuget.config, and that configuration includes a private package source that requires authentication, it fails because it can't authenticate with the private source.
The "--ignore-failed-sources" option does not have any effect.
This has been fixed in a few places, but I'm confused about where it has/has not flowed to.
The original fix was in #44309 on the main branch, which at that time was for 10.0 I believe. As part of that fix backports were initiated to both 8.0.1xx and codeflowed to 8.0.3xx. That should have automatically flowed to both 8.0.4xx and 9.0.1xx, but in my local testing with 8.0.404 and 9.0.101 I was unable to successfully install. However, on the 9.0.200 preview SDK released with VS 17.13 preview 2, I was able to install.
@edvilme can you check and see if the fix was correctly applied to 8.0.4xx and 9.0.1xx branches? If not we should trigger backports as appropriate to those branches for servicing releases.
@baronfel Hello. Yes, I remember there being some issues with the backport as the file had changed quite a lot between versions. I will take a closer look now.
Update: Seems to be working for 9.0.102-dev and 8.0.405-dev.
Describe the bug
If you run the "dotnet tool install" or "dotnet tool update" command line in a folder that contains a nuget.config, and that configuration includes a private package source that requires authentication, it fails because it can't authenticate with the private source.
The "--ignore-failed-sources" option does not have any effect.
To Reproduce
This gives the exception:
Further technical details
dotnet --info
The text was updated successfully, but these errors were encountered: