--interactive is not interactive

[wobbet]

Trying to get into private NuGet feed w/ the Credential Provider and I'm guessing it is not even being invoked.

Attempt to use --interactive and -- verbosity detailed and nothing interesting is actually provided back.

Attempt to run the credential provider directly against my feed and am being told that I don't have an up-to-date version of .NET. I do have .NET 10 as the current running version and the error message tells me I need version 8 (or higher????).

Is 10 really not sufficient?

Operating System - Windows 11
Credential Provider - 2.0.0-alpha manually installed

Note - the site docs say to run the provider directly using the netfx plugin path instead of the netcore plugin path. But the 2.0.0-alpha zip file does not have a netfx plugin path so I updated my execution to use the netcore version.

PS C:\path  dotnet --version
10.0.100

dotnet restore --interactive --verbosity detailed
    Determining projects to restore...
    C:\path\the.csproj : error NU1301:
      Unable to load the service index for source https://pathtofeed/nuget/v3/index.json.
        Response status code does not indicate success: 401 (Unauthorized).
    Failed to restore C:\Users\rsanford\Code\TrustedSide\Common\AURA.Common.MQTT\AURA.Common.MQTT.csproj (in 9.85 sec).

PS C:\path C:\Users\username\.nuget\plugins\netcore\CredentialProvider.Microsoft\CredentialProvider.Microsoft.exe  -I -V Verbose -U "https://pathtofeed/nuget/v3/index.json"
You must install or update .NET to run this application.

App: C:\Users\username\.nuget\plugins\netcore\CredentialProvider.Microsoft\CredentialProvider.Microsoft.exe
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '8.0.0' (x64)
.NET location: C:\Users\rsanford\.nuget\plugins\netcore\CredentialProvider.Microsoft\

No frameworks were found.

Learn more:
https://aka.ms/dotnet/app-launch-failed

To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=8.0.0&arch=x64&rid=win-x64&os=win10

[wobbet]

Addendum... I ran a check to see what versions of the .NET runtime are on my system and .NETCore.App version 8 is available.

PS C:\path dotnet --list-runtimes
Microsoft.AspNetCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[embetten]

@wobbet can you confirm which asset you manually installed? I was not able to reproduce this on windows 11 with the .net8 nor .win-x64 assets on a machine with only .net 10.0.101 sdks and some of the runtimes you have above

Furthermore, it looks like dotnet changed the logging. Reading through their issues I needed to run with the tl:off to see the nuget / credprovider logs. ex: dotnet restore --interactive --verbosity detailed -tl:off

We will need to update our readme information with this.

[wobbet]

I read this Stack Overflow thread and they recommended deleting hostfxr.dll as a potential resolution. That seems to have worked. I now have output. I did not look at the most recent .zip file closely to determine if that dll is in there or if it is from a previous version I had installed.

I think that the specific version from the command line is now visible as Command-line v2.0.0-alpha+9ed2abf9be344d432779713286ebed0e28cd91ba.

Should I assume that the log entries referencing on-premise Azure DevOps Server means that I can't use this tool to access my artifacts feed?

[Verbose] [CredentialProvider]Running in stand-alone mode
[Verbose] [CredentialProvider]Command-line v2.0.0-alpha+9ed2abf9be344d432779713286ebed0e28cd91ba: C:\Users\username\.nuget\plugins\netcore\CredentialProvider.Microsoft\CredentialProvider.Microsoft.dll -I -V Verbose -U https://pathtoartifacts/nuget/v3/index.json
[Verbose] [CredentialProvider]Handling auth request, Uri: https://pathtoartifacts/nuget/v3/index.json, IsRetry: True, IsNonInteractive: False, CanShowDialog: True
[Verbose] [CredentialProvider]URI: https://pathtoartifacts/nuget/v3/index.json
[Verbose] [CredentialProvider]VstsBuildTaskServiceEndpointCredentialProvider - This credential provider must be run under the Team Build tasks for NuGet with external endpoint credentials. Appropriate environment variable needs to be set.
[Verbose] [CredentialProvider]Skipping NuGetCredentialProvider.CredentialProviders.VstsBuildTaskServiceEndpoint.VstsBuildTaskServiceEndpointCredentialProvider, cannot provide credentials for https://pathtoartifacts/nuget/v3/index.json
[Verbose] [CredentialProvider]VstsBuildTaskCredentialProvider - This credential provider must be run under the Team Build tasks for NuGet. Appropriate environment variables must be set.
[Verbose] [CredentialProvider]Skipping NuGetCredentialProvider.CredentialProviders.VstsBuildTask.VstsBuildTaskCredentialProvider, cannot provide credentials for https://pathtoartifacts/nuget/v3/index.json
[Verbose] [CredentialProvider]GET https://pathtoartifacts/nuget/v3/index.json
[Verbose] [CredentialProvider]VstsCredentialProvider - Detected an on premise Azure DevOps Server.
[Verbose] [CredentialProvider]Skipping NuGetCredentialProvider.CredentialProviders.Vsts.VstsCredentialProvider, cannot provide credentials for https://pathtoartifacts/nuget/v3/index.json
[Verbose] [CredentialProvider]Unable to acquire credentials.

[embetten]

@wobbet thanks for the stack over flow link I will take a look at that running issue - but yes this cred provider is only for hosted not on prem ADO instances.

[wobbet]

The first image below is the content of the zip file I downloaded today. The second image is the contents of credential provider folder on my hard drive. There are a LOT more files on my drive than there are in that zip file.

Those files are dated 11/14/2025 (the date I probably installed them) and the ones that match the zip file are dated 12/16/2025 (today when I installed latest).

Third image shows a subset of the 11/15/2025 files which is whacked out because the files in the zip are all from 11/5/2025. Why would I have installed an earlier version? What did I do wrong here?

Anyway...

I've cleaned out my hard drive and replaced it with only what was in the zip file. It will probably run fine but right now I don't need it because I'm only accessing the on-prem server.

Many thanks!

Screenshot 1

Screenshot 2

Screenshot 3

[Frulfump]

@wobbet thanks for the stack over flow link I will take a look at that running issue - but yes this cred provider is only for hosted not on prem ADO instances.

That's not in the README.md (at least not clearly)? What do you do if you have an on prem ADO instance then?

[embetten]

For on prem - we have this small section in the readme:

but high level for nuget your options are:

1. Using nuget directly with their default credentials option.
2. This credprovider with PAT tokens set in one of the supported env variables. This would require manually rotating the PAT
3. This credprovider with the service principal env variable using certificate-based auth for local. This is outlined in the public docs