-
Notifications
You must be signed in to change notification settings - Fork 258
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
Credential provider support for dotnet.exe (cross-plat) #5447
Comments
This was never supported. Refer to documentation: https://www.visualstudio.com/en-us/docs/package/nuget/nuget-exe Unfortunately, to make use of authenticated feed on VSTS with dotnet.exe, the only option today is to specify a Personal Access Token in plain text as documented here: https://www.visualstudio.com/en-us/docs/package/nuget/dotnet-exe It does makes sense however to have a mechanism to make this scenario work with dotnet.exe. |
Adding this support will help greatly those using dotnet CLI. |
It appears Credential Providers are working for
Environment:
|
I suspect you've got a credential stashed somewhere on disk already, or the packages are already cached. We're working right now to bring cross-plat credential provider support to dotnet, but it hasn't shipped yet. |
Duplicate of #6486. @livarcocc Can we close this one? |
Sounds good to me. |
@alexmullans i had the packages cached. i cleared my thanks for tracking this; #6486 will be very welcomed. |
From @craigb on June 17, 2017 0:44
Steps to reproduce
dotnet restore
Expected behavior
I would expect it to auth and retrieve information about packages just like
nuget.exe restore
.Actual behavior
Environment data
nuget help
:NuGet Version: 4.1.0.2450
dotnet --info
output:.NET Command Line Tools (1.0.4)
Product Information:
Version: 1.0.4
Commit SHA-1 hash: af1e6684fd
Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\1.0.4
Copied from original issue: dotnet/cli#6916
The text was updated successfully, but these errors were encountered: