You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
NuGet team provides an updated version of the Credential Provider that includes x86 support. #638
Goal: The MS NuGet Credential Provider no longer ships a self‑contained x86 build. Our debugger relies on this credential provider and installs on x86, amd64, and arm64, so the removal of x86 support causes a regression for our scenario. We are submitting this request for the NuGet team to restore x86 support in their current versions. Why: As a temporary workaround, we are using the last available version of the credential provider that still includes x86 support. Without x86 support in newer versions, we are forced to remain on older packages, which limits our ability to update and maintain compatibility. Acceptance Criteria: NuGet team provides an updated version of the Credential Provider that includes x86 support. Outcome: The Debugging tools can consume the latest NuGet Credential Provider across all three architectures (x86, amd64, arm64), removing our dependency on older versions.
Quick clarification: Is this just a feature request to add the win-x86 and win-arm64 RIDs?
I’m asking because we have not previously shipped a self‑contained win-x86/arm64 build, so there wouldn’t have been existing support to remove. As a result, I’m not sure where a regression would be occurring.
If you think you can't use the existing deployments you have for arm64 for Windows, then our answer is "yes" as we need all 3 flavors for Windows installs.
Thanks!
As debugger install should be non-invasive as much as possible, we prefer to not ask the user to install .NET versions in order to be able to use the debugger.
This support is now available as pre-release in the 2.0.1. We will flip to latest and publish the dotnet tool after at least 48 hour waiting period to try out the pre-release version you need to specify ex:
Activity
embetten commentedon Feb 11, 2026
Quick clarification: Is this just a feature request to add the win-x86 and win-arm64 RIDs?
I’m asking because we have not previously shipped a self‑contained win-x86/arm64 build, so there wouldn’t have been existing support to remove. As a result, I’m not sure where a regression would be occurring.
We do continue to ship non‑self‑contained builds, which should work cross‑platform as long as the appropriate .NET runtime is available. These can be found in the release assets as: Microsoft.{framework}.NuGet.CredentialProvider.zip
Example:
https://github.com/microsoft/artifacts-credprovider/releases/download/v2.0.0/Microsoft.Net8.NuGet.CredentialProvider.zip
TedyHH commentedon Feb 11, 2026
If you think you can't use the existing deployments you have for arm64 for Windows, then our answer is "yes" as we need all 3 flavors for Windows installs.
Thanks!
TedyHH commentedon Feb 11, 2026
As debugger install should be non-invasive as much as possible, we prefer to not ask the user to install .NET versions in order to be able to use the debugger.
Fix win-arm64 self-contained packaged architecture (#647)
embetten commentedon Mar 18, 2026
This support is now available as pre-release in the 2.0.1. We will flip to latest and publish the dotnet tool after at least 48 hour waiting period to try out the pre-release version you need to specify ex:
iex "& { $(irm https://aka.ms/install-artifacts-credprovider.ps1) } -Version 2.0.1 -Force"
embetten commentedon Mar 24, 2026
Tedy Hroulev (@TedyHH) 2.0.1 is now marked as latest. Closing please re-open if you run into any issues.