Open KirillOsenkov opened 2 days ago
If the user does msbuild /r /p:NuGetInteractive=true I fully expect the NuGet Credential Provider to show the dialog instead of device flow for auth to Azure DevOps, at least on Windows.
msbuild /r /p:NuGetInteractive=true
However this here defaults it to false: https://github.com/NuGet/NuGet.Client/blob/9dd33574b0cf5110692ee8e9401a39857fb5523a/src/NuGet.Core/NuGet.Credentials/DefaultCredentialServiceUtility.cs#L64
If the user is specifying NuGetInteractive it's an explicit command that not only permits, but demands UI. Device Flow is awful in terms of UX.
There is a workaround, but it's obscure: set NUGET_CREDENTIALPROVIDER_FORCE_CANSHOWDIALOG_TO=true
set NUGET_CREDENTIALPROVIDER_FORCE_CANSHOWDIALOG_TO=true
This should be implemented for both msbuild as well as dotnet (perhaps nuget.exe too)
msbuild
dotnet
See https://github.com/microsoft/artifacts-credprovider/issues/465 for details
Issue is missing Type label, remember to add a Type label
If the user does
msbuild /r /p:NuGetInteractive=true
I fully expect the NuGet Credential Provider to show the dialog instead of device flow for auth to Azure DevOps, at least on Windows.However this here defaults it to false: https://github.com/NuGet/NuGet.Client/blob/9dd33574b0cf5110692ee8e9401a39857fb5523a/src/NuGet.Core/NuGet.Credentials/DefaultCredentialServiceUtility.cs#L64
If the user is specifying NuGetInteractive it's an explicit command that not only permits, but demands UI. Device Flow is awful in terms of UX.
There is a workaround, but it's obscure:
set NUGET_CREDENTIALPROVIDER_FORCE_CANSHOWDIALOG_TO=true
This should be implemented for both
msbuild
as well asdotnet
(perhaps nuget.exe too)