Skip to content
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

Interactive UI question #68

Closed
flcdrg opened this issue Feb 18, 2019 · 2 comments
Closed

Interactive UI question #68

flcdrg opened this issue Feb 18, 2019 · 2 comments

Comments

@flcdrg
Copy link

flcdrg commented Feb 18, 2019

I'm looking to migrate from Microsoft.VisualStudio.Services.NuGet.CredentialProvider, but I'm a bit unclear as to what UI I should get when running in interactive mode.

Should I see a pop-up dialog (like I would get with the old provider), or is it just a console-based prompt?

Or does it vary depending on whether I run dotnet restore or nuget restore?

@flcdrg flcdrg changed the title Interactive UI Interactive UI question Feb 18, 2019
@satbai
Copy link
Contributor

satbai commented Feb 20, 2019

It depends. With Windows using nuget.exe or msbuild in most cases you'll get a popup dialog. And with dotnet you'll get a device flow prompt in the console that will direct you to authenticate through a browser. Also, we'll in most cases try to do a non-interactive auth first and if that isn't successful we'll fall back to the popup dialog and then the device flow.

@flcdrg
Copy link
Author

flcdrg commented Feb 20, 2019

I think that makes sense. The code I'm updating is using .NET Core, whereas the code that I'd used the old credential provider was using .NET Framework/NuGet.exe - so I was surprised at first not to get a similar dialog popup.

Maybe adding some examples to the README or documentation (if this ends up on docs) would be useful to set expectations.

@flcdrg flcdrg closed this as completed Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants