SDK Resolver Failure in .NET 7 and .NET 6

Home Q&A SDK Resolver Failure in .NET 7 and .NET 6

Issue Overview

After installing the .NET 7.0.100 SDK, existing .NET applications built with .NET 6 or .NET 7 fail to load in Visual Studio 2022 or JetBrains Rider. The following error is commonly observed:

SDK Resolver Failure: “The SDK resolver \”Microsoft.DotNet.MSBuildSdkResolver\”
failed while attempting to resolve the SDK \”Microsoft.NET.Sdk\”.

Exception: “Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException:
Workload definition ‘wasm-tools’ in manifest ‘microsoft.net.workload.mono.toolchain.net7’ conflicts
with manifest ‘microsoft.net.workload.mono.toolchain’”

Cause

The issue occurs due to conflicting workload manifest definitions between .NET 6 and .NET 7 SDKs. The workload wasm-tools are defined in both the .NET 7 and .NET 6 manifests, causing a conflict during workload resolution.

Steps to Resolve

1. Clear Workload Cache

Clear the workload cache to remove potentially corrupted or conflicting workloads:

dotnet workload clean

2. Uninstall Workloads

Uninstall all workloads to reset the installed workloads:

dotnet workload uninstall –all

3. Repair .NET SDK Installation

Repair the .NET SDK installation by re-running the installer from the official .NET download page.

4. Install Required Workloads

Reinstall only the required workloads for your application:

dotnet workload install wasm-tools

5. Verify Installation

Verify that the correct workloads are installed:

dotnet workload list

6. Restart IDE

Restart Visual Studio 2022 or JetBrains Rider to ensure that the new workload configurations are applied.

Additional Troubleshooting

Check if the environment variable DOTNET_CLI_HOME is set correctly.
Ensure that no custom global.json file is forcing the use of an incompatible SDK version.
Update Visual Studio 2022 to the latest version, as it may include patches for SDK compatibility.