Open ld0614 opened 5 years ago
@ld0614 thanks for opening this issue, and providing detailed explanation--it is very helpful! We will try to make this change when possible, but please note that we do not have any planned releases for PowerShell 2.x (we are currently undergoing a major re-architecture for PowerShell Get 3.0)
One work around for this is to set your NUGET_PLUGIN_PATHS to .nuget\plugins\netfx\CredentialProvider.Microsoft\CredentialProvider.Microsoft.exe in other words put $Env:NUGET_PLUGIN_PATHS = "fullpath\.nuget\plugins\netfx\CredentialProvider.Microsoft\CredentialProvider.Microsoft.exe"
in your PowerShell profile
Steps to reproduce
Install fresh Windows 10 1903 with no additional software
Expected behavior
Actual behaviour
Looking at the code it appears that only .nuget/plugins/netcore/CredentialProvider.Microsoft/CredentialProvider.Microsoft.dll in the user profile is checked. The advice from https://github.com/microsoft/artifacts-credprovider is that the NetFx package is required as such this was downloaded to .nuget\plugins\netfx\CredentialProvider.Microsoft and includes the CredentialProvider.Microsoft.exe file. On a standard Windows 10 device the dotnet application is not available, therefore the error received is highly confusing (implicit dependency on dotnet application) and as there is a supported approach avoiding the requirement of dotnet, IMO this should be silently checked for.
Possible Fix
Starts Line 9252 of Version 2.2.1
Environment data