search

dotnet / sdk

Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
https://dot.net/core
MIT License
2.75k stars 1.07k forks source link

Cannot load or run lots of my projects in my solution after installing .NET 7 #28947

Closed sencagri closed 2 years ago

sencagri commented 2 years ago

Edit + General Resolution (from @nagilson):

This is now documented as a known issue for .NET 7 and a resolution is provided here.

Describe the bug

I just installed the last update of visual studio. Then, this happened, I cannot open my projects. image C:\Users\PC2\source\repos\AktifPOS\AktifBarkod.AktifPOS.Data\AktifBarkod.AktifPOS.Data.csproj : error : 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' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain\WorkloadManifest.json] conflicts with manifest 'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json] at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests() at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, String sdkVersion, String userProfileDir) at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVersion, String userProfileDir) at Microsoft.DotNet.MSBuildSdkResolver.DotNetMSBuildSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext context, SdkResultFactory factory) at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.TryResolveSdkUsingSpecifiedResolvers(IList`1 resolvers, Int32 submissionId, SdkReference sdk, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath, Boolean interactive, Boolean isRunningInVisualStudio, SdkResult& sdkResult)"" C:\Users\PC2\source\repos\AktifPOS\AktifBarkod.AktifPOS.Data\AktifBarkod.AktifPOS.Data.csproj

image

To Reproduce

Exceptions (if any)

Further technical details

Runtime Environment: OS Name: Windows OS Version: 10.0.22621 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\7.0.100\

Host: Version: 7.0.0 Architecture: x64 Commit: d099f075e4

.NET SDKs installed: 3.1.424 [C:\Program Files\dotnet\sdk] 5.0.301 [C:\Program Files\dotnet\sdk] 5.0.414 [C:\Program Files\dotnet\sdk] 6.0.100-rc.1.21463.6 [C:\Program Files\dotnet\sdk] 6.0.200 [C:\Program Files\dotnet\sdk] 7.0.100-rc.2.22477.23 [C:\Program Files\dotnet\sdk] 7.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed: Microsoft.AspNetCore.App 3.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.31 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 5.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.0-rc.1.21452.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 7.0.0-rc.2.22476.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.1.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.31 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.0-rc.1.21451.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 7.0.0-rc.2.22472.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.1.16 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 3.1.23 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 3.1.30 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 3.1.31 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.0-rc.1.21451.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 7.0.0-rc.2.22472.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found: arm64 [C:\Program Files\dotnet] registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\arm64\InstallLocation] x86 [C:\Program Files (x86)\dotnet] registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables: Not set

global.json file: Not found

Learn more: https://aka.ms/dotnet/info

Download .NET: https://aka.ms/dotnet/download PS C:\Users\PC2>

dotnet-issue-labeler[bot] commented 2 years ago

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

xt0rted commented 2 years ago

Just updated VS and I'm getting the same error when I open my .net 6 projects (without a global.json), as well as when I try to run dotnet ... commands in projects where the sdk was bumped to 7.0.100, switching back to 6.0.402 results in the errors going away.

Project without a global.json targeting net6.0:

❯⠀dotnet new globaljson
Unhandled exception: Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException: Workload definition 'wasm-tools' in manifest 'microsoft.net.workload.mono.toolchain' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain\WorkloadManifest.json] conflicts with manifest 'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json]
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, String sdkVersion, String userProfileDir)
   at Microsoft.DotNet.Workloads.Workload.List.WorkloadInfoHelper..ctor(VerbosityOptions verbosity, String targetSdkVersion, Nullable`1 verifySignatures, IReporter reporter, IWorkloadInstallationRecordRepository workloadRecordRepo, String currentSdkVersion, String dotnetDir, String userProfileDir, IWorkloadResolver workloadResolver)
   at Microsoft.DotNet.Cli.NewCommandParser.CreateHost(Boolean disableSdkTemplates, Boolean disableProjectContext, FileInfo projectPath, FileInfo outputPath, LogLevel logLevel)
   at Microsoft.DotNet.Cli.NewCommandParser.<GetCommand>g__GetEngineHost|11_0(ParseResult parseResult)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand.CreateEnvironmentSettings(GlobalArgs args, ParseResult parseResult)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand`1.InvokeAsync(InvocationContext context)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand`1.Invoke(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.DotNet.Cli.Parser.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.CommandLineBuilderExtensions.<>c__DisplayClass11_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__17_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.CommandLineBuilderExtensions.<>c__DisplayClass15_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.CommandLineBuilderExtensions.<>c__DisplayClass7_0.<<UseExceptionHandler>b__0>d.MoveNext()

Project with a global.json pinned to 7.0.100 and targeting net6.0:

❯⠀dotnet tool restore
C:\Users\brian\AppData\Local\Temp\c296991e-f923-4229-8180-492a3f6e3183\restore.csproj(5,31): error MSB4242: SDK Resolver Failure: "The SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" failed while attempting to resolve the SDK "Microsoft.NET
.SdC:\Users\brian\AppData\Local\Temp\6612f8be-9856-44c2-b7fb-d88752dc0763\restore.csproj(5,31): error MSB4242: SDK Resolver Failure: "The SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" 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' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workloa 
d.mono.toolchain\WorkloadManifest.json] conflicts with manifest 'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json]
C:\Users\brian\AppData\Local\Temp\6612fC:\Users\brian\AppData\Local\Temp\27a236df-c809-48b8-b7a0-e6e7e874c576\restore.csproj(5,31): error MSB4242: SDK Resolver Failure: "The SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" 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' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workloa 
d.mono8be-9856-44c2-b7fb-d88752dc0763\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
C:\Users\brian\AppData\Local\Temp\6612f8be-9856-44c2-b7fb-d88752dc0763\restore.csproj(5,31): erk". Exception: "Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException: Workload definition 'wasm-tools' in manifest 'microsoft.net.workload.mono.toolchain' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workloa
d.mono.toolchain\WorkloadManifest.json] conflicts with manifest 'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json]
C:\Users\brian\AppData\Local\Temp\27a23ror MSB4242:    at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, Strin
g sdkVersion, String userProfileDir)
C:\Users\brian\AppData\Local\Temp\6612f8be-9856-44c2-b7fb-d88752dc0763\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVe 
rsion, String userProfileDir)
C:\Users\brian\AppData\Local\Tem6df-c809-48b8-b7a0-e6e7e874c576\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
C:\Users\brian\AppData\Local\Temp\27a236df-c809-48b8-b7a0-e6e7e874c576\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, Strin 
g sdkVersion, String userProfileDir)
C:\Users\brian\AppData\Local\Temp\27a236df-c809-48b8-b7a0-e6e7e874c576\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVe 
rsion, String userProfileDir)
C:\Users\brian\AppData\Local\Temp\27a236df-c809-48b8-b7a0-e6e7e874c576\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.WorkloadSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext resolverContext, S 
dkResultFactory factory)
C:\Users\p\6612f8be-9856-44c2-b7fb-d88752dc0763\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.WorkloadSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext resolverContext, S
dkResultFactory factory)
C:\Users\.toolchain\WorkloadManifest.json] conflicts with manifest 'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json]
C:\Users\brian\AppData\Local\Temp\c2969brian\AppData\Local\Temp\27a236df-c809-48b8-b7a0-e6e7e874c576\restore.csproj(5,31): error MSB4242:    at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.TryResolveSdkUsingSpecifiedResolvers(IList`1 resolvers, Int32 submissionId, SdkR
eference sdkbrian\AppData\Local\Temp\6612f8be-9856-44c2-b7fb-d88752dc0763\restore.csproj(5,31): error MSB4242:    at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.TryResolveSdkUsingSpecifiedResolvers(IList`1 resolvers, Int32 submissionId, SdkR
eference sdk91e-f923-4229-8180-492a3f6e3183\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
C:\Users\brian\AppData\Local\Temp\c296991e-f923-4229-8180-492a3f6e3183\restore.csproj(5,31): er, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath, Boolean interactive, Boolean isRunningInVisualStudio, SdkResult& sdkResult)""
, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath, Boolean interactive, Boolean isRunningInVisualStudio, SdkResult& sdkResult)""
ror MSB4242:    at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, Strin
g sdkVersion, String userProfileDir)
C:\Users\brian\AppData\Local\Temp\c296991e-f923-4229-8180-492a3f6e3183\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVe 
rsion, String userProfileDir)
C:\Users\brian\AppData\Local\Temp\c296991e-f923-4229-8180-492a3f6e3183\restore.csproj(5,31): error MSB4242:    at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.WorkloadSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext resolverContext, S 
dkResultFactory factory)
C:\Users\brian\AppData\Local\Temp\c296991e-f923-4229-8180-492a3f6e3183\restore.csproj(5,31): error MSB4242:    at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.TryResolveSdkUsingSpecifiedResolvers(IList`1 resolvers, Int32 submissionId, SdkR 
eference sdk, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath, Boolean interactive, Boolean isRunningInVisualStudio, SdkResult& sdkResult)""

Package "mockaco" failed to restore, due to Microsoft.DotNet.ToolPackage.ToolPackageException: The tool package could not be restored.
   at Microsoft.DotNet.Tools.Tool.Install.ProjectRestorer.Restore(FilePath project, PackageLocation packageLocation, String verbosity)
   at Microsoft.DotNet.ToolPackage.ToolPackageInstaller.InstallPackageToExternalManagedLocation(PackageLocation packageLocation, PackageId packageId, VersionRange versionRange, String targetFramework, String verbosity)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.InstallPackages(ToolManifestPackage package, Nullable`1 configFile)
Package "run-script" failed to restore, due to Microsoft.DotNet.ToolPackage.ToolPackageException: The tool package could not be restored.
   at Microsoft.DotNet.Tools.Tool.Install.ProjectRestorer.Restore(FilePath project, PackageLocation packageLocation, String verbosity)
   at Microsoft.DotNet.ToolPackage.ToolPackageInstaller.InstallPackageToExternalManagedLocation(PackageLocation packageLocation, PackageId packageId, VersionRange versionRange, String targetFramework, String verbosity)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.InstallPackages(ToolManifestPackage package, Nullable`1 configFile)
Package "startup-projects" failed to restore, due to Microsoft.DotNet.ToolPackage.ToolPackageException: The tool package could not be restored.
   at Microsoft.DotNet.Tools.Tool.Install.ProjectRestorer.Restore(FilePath project, PackageLocation packageLocation, String verbosity)
   at Microsoft.DotNet.ToolPackage.ToolPackageInstaller.InstallPackageToExternalManagedLocation(PackageLocation packageLocation, PackageId packageId, VersionRange versionRange, String targetFramework, String verbosity)
   at Microsoft.DotNet.Tools.Tool.Restore.ToolRestoreCommand.InstallPackages(ToolManifestPackage package, Nullable`1 configFile)

Tool 'rimraf' (version '0.1.0') was restored. Available commands: rimraf

Restore partially failed.
pascallapradebrite4 commented 2 years ago

I tried to hack the problem locally pending a proper fix.

My error message states that there is a conflict between two manifests (macOS arm64, hence the paths): /usr/local/share/dotnet/sdk-manifests/7.0.100/microsoft.net.workload.mono.toolchain/WorkloadManifest.json [...] conflicts with manifest [...] /usr/local/share/dotnet/sdk-manifests/7.0.100/microsoft.net.workload.mono.toolchain.net7/WorkloadManifest.json

I'm not entirely sure how these are intended to work, but I saw "there is a conflict" and thought "what if I remove one of them?".

So I deleted (moved elsewhere just in case) the .net7 manifest directory specifically, and everything is back to working.

sudo mv /usr/local/share/dotnet/sdk-manifests/7.0.100/microsoft.net.workload.mono.toolchain.net7 ~/dotnet.bak

Now, dotnet restore, dotnet build and dotnet run all work.

Obviously this is just a temporary hack, your mileage may vary, and I don't know if this can damage some setups, I'm not endorsing that everyone affected should do this while waiting for the fix. Just hoping it can help some people in the meantime.

Edit: I should mention: macOS 13.0 arm64, .NET 7.0 SDK arm64 GA directly, no Visual Studio, here are all my SDKs installed:

6.0.100 [/usr/local/share/dotnet/sdk]
6.0.101 [/usr/local/share/dotnet/sdk]
6.0.102 [/usr/local/share/dotnet/sdk]
6.0.200 [/usr/local/share/dotnet/sdk]
6.0.201 [/usr/local/share/dotnet/sdk]
6.0.300 [/usr/local/share/dotnet/sdk]
6.0.301 [/usr/local/share/dotnet/sdk]
7.0.100-preview.5.22307.18 [/usr/local/share/dotnet/sdk]
7.0.100-preview.6.22352.1 [/usr/local/share/dotnet/sdk]
7.0.100-preview.7.22377.5 [/usr/local/share/dotnet/sdk]
7.0.100-rc.1.22431.12 [/usr/local/share/dotnet/sdk]
7.0.100-rc.2.22477.23 [/usr/local/share/dotnet/sdk]
7.0.100 [/usr/local/share/dotnet/sdk]
xt0rted commented 2 years ago

Following up on the workaround by @pascallapradebrite4 if I remove C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain then things start to work again. Removing the microsoft.net.workload.mono.toolchain.net7 folder didn't help in my instance.

Contents of C:\Program Files\dotnet\sdk-manifests\7.0.100:

❯⠀dir /B
microsoft.net.sdk.android
microsoft.net.sdk.ios
microsoft.net.sdk.maccatalyst
microsoft.net.sdk.macos
microsoft.net.sdk.maui
microsoft.net.sdk.tvos
microsoft.net.workload.emscripten
microsoft.net.workload.emscripten.net6
microsoft.net.workload.emscripten.net7
microsoft.net.workload.mono.toolchain
microsoft.net.workload.mono.toolchain.net6
microsoft.net.workload.mono.toolchain.net7
❯⠀dotnet --info
.NET SDK:
 Version:   7.0.100
 Commit:    e12b7af219

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\7.0.100\

Host:
  Version:      7.0.0
  Architecture: x64
  Commit:       d099f075e4

.NET SDKs installed:
  2.1.818 [C:\Program Files\dotnet\sdk]
  3.0.103 [C:\Program Files\dotnet\sdk]
  3.1.424 [C:\Program Files\dotnet\sdk]
  5.0.203 [C:\Program Files\dotnet\sdk]
  5.0.214 [C:\Program Files\dotnet\sdk]
  5.0.303 [C:\Program Files\dotnet\sdk]
  5.0.408 [C:\Program Files\dotnet\sdk]
  6.0.100-preview.3.21202.5 [C:\Program Files\dotnet\sdk]
  6.0.202 [C:\Program Files\dotnet\sdk]
  6.0.203 [C:\Program Files\dotnet\sdk]
  6.0.305 [C:\Program Files\dotnet\sdk]
  6.0.401 [C:\Program Files\dotnet\sdk]
  6.0.402 [C:\Program Files\dotnet\sdk]
  7.0.100-preview.6.22352.1 [C:\Program Files\dotnet\sdk]
  7.0.100 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.27 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.27 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.0-preview.3.21201.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.0-preview.6.22330.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.27 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.0-preview.3.21201.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.0-preview.6.22324.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.30 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.16 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.0-preview.3.21201.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.0-preview.6.22351.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  arm64 [C:\Program Files\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\arm64\InstallLocation]
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download
xt0rted commented 2 years ago

Just realized there was still a preview version of the sdk installed. I assumed this would be cleaned up when updating since I never manually installed this, but I guess it wasn't. After updating I did restart like it suggested so it's not due to a cleanup task not running yet.

I manually uninstalled 7.0.100-preview.6.22352.1 and that removes microsoft.net.workload.emscripten and microsoft.net.workload.mono.toolchain from C:\Program Files\dotnet\sdk-manifests\7.0.100 which fixed the issue for me.

nyan-cat commented 2 years ago

@xt0rted faced same issue, followed your instruction. deleted the folder, and everything is fine again :)

sencagri commented 2 years ago

I'm not sure about deleting anything that I don't know. I'm scared if it makes it worse.

nyan-cat commented 2 years ago

@sencagri

I'm not sure about deleting anything that I don't know. I'm scared if it makes it worse.

Don't delete, but move it to some other outer folder. If things get worse - just move it back :)

xt0rted commented 2 years ago

@sencagri you have a pre-release version of dotnet 7 installed (7.0.100-rc.2.22477.23), uninstall that and see if the errors persist. When I uninstalled the preview that was left on my machine the issues went away.

nagilson commented 2 years ago

Sorry you're dealing with this; it sucks to get an update and then suddenly have your things break.

The official guidance we have for you atm is to uninstall any preview SDKs, like @xt0rted mentioned. Some workload files in some of the preview SDKs will conflict with the RTM / official .NET 7 SDK release. @pascallapradebrite4's suggestion to delete the microsoft.net.workload.mono.toolchain is also valid and we have been telling people internally to do the same.

As for why, I believe In the middle of preview development some workload content got renamed, with .net7.0 being appended to the end. The reason this happened (multi targeting) is convoluted to say the least and someone else from the team could probably explain it better. We've been having discussions about how to prevent the same thing happening when folks upgrade to .NET 8. We are also considering dotnet workload clean which could fix this for you. Thanks, and please let us know of any other feedback or questions here!

is-aka-konor commented 2 years ago

In my case, on Mac I had to

  1. Delete all unused Dotnet runtimes & SDKs via dotnet-core-uninstall (https://github.com/dotnet/cli-lab/releases)
  2. Remove all folders in /usr/local/share/dotnet/sdk-manifests
  3. Re-install required .Net SDKs
sencagri commented 2 years ago

I have deleted the folders you mentioned. Now I'm able to load projects but cannot build anymore. I am getting these errors:

4>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Android is not installed. Please restore and try again.
4>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Maui.Core is not installed. Please restore and try again.
4>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Maui.Controls is not installed. Please restore and try again.
4>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Maui.Essentials is not installed. Please restore and try again.

What is "restore" mean?

is-aka-konor commented 2 years ago

What is "restore" mean?

Unfortunately, the dotnet documentation isn’t clear about it.

Have you reinstalled the SDKs? Have you tried to restore NuGet packages? Have you tried to repair your visual studio installation?

walterlv commented 2 years ago

I have the same issue.

Fortunately, I have two computers running the same version of .NET 7.0 / Visual Studio 2022 with the same workloads. One works fine and the other is broken. I checked the path C:\Program Files\dotnet\sdk-manifests\7.0.100 and find that the PC with broken Visual Studio has an extra folder named microsoft.net.workload.mono.toolchain.

I deleted the extra folder, and now the .NET 7.0 / Visual Studio works fine.

image

The error message:

🤣:  dotnet new --help
Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException: 清单“wasm-tools”[microsoft.net.workload.mono.toolchain] 中的工作负载定义“C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain\WorkloadManifest.json”与清单“microsoft.net.workload.mono.toolchain.net7”[C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json] 冲突
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, String sdkVersion, String userProfileDir)
   at Microsoft.DotNet.Workloads.Workload.List.WorkloadInfoHelper..ctor(VerbosityOptions verbosity, String targetSdkVersion, Nullable`1 verifySignatures, IReporter reporter, IWorkloadInstallationRecordRepository workloadRecordRepo, String currentSdkVersion, String dotnetDir, String userProfileDir, IWorkloadResolver workloadResolver)
   at Microsoft.DotNet.Cli.NewCommandParser.CreateHost(Boolean disableSdkTemplates, Boolean disableProjectContext, FileInfo projectPath, FileInfo outputPath, LogLevel logLevel)
   at Microsoft.DotNet.Cli.NewCommandParser.<GetCommand>g__GetEngineHost|11_0(ParseResult parseResult)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand.CreateEnvironmentSettings(GlobalArgs args, ParseResult parseResult)
   at Microsoft.TemplateEngine.Cli.Commands.NewCommand.<CustomHelpLayout>b__31_0(HelpContext context)
   at Microsoft.DotNet.Cli.Parser.DotnetHelpBuilder.Write(HelpContext context)
   at System.CommandLine.Invocation.InvocationPipeline.GetExitCode(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<Invoke>g__FullInvocationChain|3_0(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.Invoke(IConsole console)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)
DerekZiemba commented 2 years ago

Following up on the workaround by @pascallapradebrite4 if I remove C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain then things start to work again. Removing the microsoft.net.workload.mono.toolchain.net7 folder didn't help in my instance.

@xt0rted FINALLY A (partial) SOLUTION! Notes:

I've had this (or very similar) issue since June 15 2022 (judging by folder dates modified) which coincides with the Jun 14, 2022 release of .NET 7 Preview 5. I had originally tried the .NET 7.0 Preview due to bugs in .NET6.0 that prevented publishing Trimmed & SelfContained executables. My VS2022Pro has since been broke due to MSBuildSdkResolver errors and I've been forced to use VS2022ProPreview ever since. I had tried: a complete reinstall, devenv /resetuserdata, & using a different /RootSuffix .

Today I upgraded to dotnet7.0 RTM. This broke BOTH VS2022Pro & VS2022ProPreview so I'm now dead in the water. This time though, Google actually has search result because everyone's been upgrading to dotnet7.0.
However, this new error is slightly different than the original. The original was a lot less helpful as it did not mention anything about wasm-tools or microsoft.net.workload.mono.toolchain. What I could still find in my clipboard history is just:

Microsoft.VisualStudio.ProjectSystem.Query.QueryExecutionException: SDK Resolver Failure: "The SDK resolver "Microsoft.DotNet.MSBuildSdkResolver" failed while attempting to resolve the SDK

My new issue / return of the Publish issue:

I originally went to VS2022ProPreview with .NET 7.0 Preview 5 because publishing with .NET6.0 would always result in:

Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. A diagnostic log has been written to the following location: "C:\Users\Derek\AppData\Local\Temp\tmp5DAA.tmp"

Contents of C:\Users\Derek\AppData\Local\Temp\tmp5DAA.tmp:

System.AggregateException: One or more errors occurred. ---> Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. --- End of inner exception stack trace --- ---> (Inner Exception #0) Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details. <---

Microsoft.WebTools.Shared.Exceptions.WebToolsException: Publish has encountered an error. We were unable to determine the cause of the error. Check the output log for more details.

Build Output:

2>Assets file '.\launcher.out\obj\publish\win-x86\project.assets.json' doesn't have a target for 'net7.0'. Ensure that restore has run and that you have included 'net7.0' in the TargetFrameworks for your project. Build has been canceled.

Yet, the project builds just fine in Debug & Release mode. It's only for publish that 'project.assets.json' doesn't have a target for 'net7.0'.

Publish worked before the update.

@walterlv or anyone else. Can you verify Publish still works after deleting the mono folder?

sencagri commented 2 years ago

I was able to build and debug some of my projects before deleting the folder mentioned above. After deleting, I cannot debug & build or publish.

Things I have tried but build: Tried reinstalling VS, Repairing VS, Delete and reinstall nuget packages, Cleaning solution and project and also deleting obj and bin folders, Try to build after removing dotnet sdks, Try to build after reinstalling dotnet sdks, I have downloaded and installed all windows updates.

What about installing a zero Windows 10 & 11 ? What is the fastest way to workaround before official solution?

alexeyzimarev commented 2 years ago

Delete all unused Dotnet runtimes & SDKs via dotnet-core-uninstall

The uninstall tool has an artificial limitation not to uninstall SDK 7+ versions, and the issue is open since August (https://github.com/dotnet/cli-lab/issues/230). Ironically, I tried cloning the repository to apply the fix and run it, but it failed to build because of the exact issue described here.

walterlv commented 2 years ago

@DerekZiemba Any suggestions for me to verify the Publish?

I've published some of my WPF / MAUI / Asp.NET projects and succeeded. I can't figure out which type of project will use the mono workload to verify the lack of the deleted folder.

vshapenko commented 2 years ago

Have same issue, deleting microsoft.net.workload.mono.toolchain helped alot on my mac. Kudos to @pascallapradebrite4 for workaround. Anyway, i am guessing that one of net 7/6 preview versions had improper folder name

DerekZiemba commented 2 years ago

@walterlv I'm just publishing a console app that doesn't show a window. Its purpose is a launcher and updater.
Here's the publish profile. Be sure to change the extension to .pubxml net7.0-x86.md

Also I checked my shadow volume checkpoint history and my microsoft.net.workload.mono.toolchain file did not change. However, my VS2022 install that was relying on those has been broken for months which is why I was using VS2022 Preview on 7.0.100-rc2, which notably did not contain:

microsoft.net.workload.emscripten
microsoft.net.workload.emscripten.net6
microsoft.net.workload.emscripten.net7
microsoft.net.workload.mono.toolchain
microsoft.net.workload.mono.toolchain.net6
microsoft.net.workload.mono.toolchain.net7

image

There's also a stackoverflow thread about this https://stackoverflow.com/questions/74365441/sdk-resolver-failure-net-7-net-6

They said to uninstall the previews. Which I do have installed and am in the process of removing. Will report back if it fixes things. image

EDIT: Everything works for me now. Better than it ever has actually. I've been putting up with an issue where dotnet core, standard, new framework , & anything except dotnet framework <4.8.1 project templates wouldn't appear in the new project menus. That's fixed too now.

To get it to publish I had to remove the following from the project file

    <TargetFramework>net7.0-windows10.0.17763.0</TargetFramework>
    <SupportedOSPlatformVersion>7.0</SupportedOSPlatformVersion>
huoyaoyuan commented 2 years ago

Also hitting this. The previously installed preview SDK was overridden by Visual Studio installed SDK, but the extra folder wasn't removed.

Hyper-Dragon commented 2 years ago

I manually uninstalled 7.0.100-preview.6.22352.1 and that removes microsoft.net.workload.emscripten and microsoft.net.workload.mono.toolchain from C:\Program Files\dotnet\sdk-manifests\7.0.100 which fixed the issue for me.

@xt0rted Many thanks. It was Microsoft .NET SDK 7.0.100-preview.3.22179.4 in my case.

ptr727 commented 2 years ago

metoo, can't open projects after updating VS:

C:\Users\piete\source\repos\ptr727\PlexCleaner\PlexCleaner\PlexCleaner.csproj : error  : 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' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain\WorkloadManifest.json] conflicts with manifest 'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json]
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, String sdkVersion, String userProfileDir)
   at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVersion, String userProfileDir)
   at Microsoft.DotNet.MSBuildSdkResolver.DotNetMSBuildSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext context, SdkResultFactory factory)
   at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.TryResolveSdkUsingSpecifiedResolvers(IList`1 resolvers, Int32 submissionId, SdkReference sdk, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath, Boolean interactive, Boolean isRunningInVisualStudio, SdkResult& sdkResult)""  C:\Users\piete\source\repos\ptr727\PlexCleaner\PlexCleaner\PlexCleaner.csproj
nagilson commented 2 years ago

@sencagri

I'm going to pin the solution that worked for most people by editing it and appending it to the top of your comment. Following up here to try to help with your specific scenario. I saw the error you mentioned here:

4>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Android is not installed. Please restore and try again

I'm pretty sure the intention of that error was to get you to do a nuget restore but I'm not sure if that will really solve the situation as your machine is probably in a pretty weird state. I saw you mentioned reinstalling the .NET 7 SDK but more information here would be helpful.

Please try doing an uninstall of all .NET 7 SDKs, since you're on windows you can easily do this in the Add or Remove Programs window. image Visual Studio may also have .NET 7 preview SDKs installed, after the uninstall go to the VS Installer, Modify existing VS Installations, Individual Components, and make sure there are no remaining .NET 7 SDKs.

image

Then re-install a single copy of the .NET 7 RTM SDK. If it doesn't work with a clean installation, please report back what errors you get trying to build so we can take another look.

DimaViaroukin commented 2 years ago

Had the same problem on Macbook Arm64

What helped me:

  1. Remove VS 2022 for Mac
  2. Removing .net sdk and runtimes (https://learn.microsoft.com/en-gb/dotnet/core/additional-tools/uninstall-tool?tabs=macos and some manual scripts to remove .net 7 and dotnet folders in /etc and /usr/local/share folders)
  3. Install .net 7 and only after that step to install .net 6
  4. Intall VS for Mac.

Also i checked in Rider 2022.2 and 2022.3 EAP 7 and works fine there as well

sencagri commented 2 years ago

I have installed everything from zero. Now everything works. Thanks for help.

nagilson commented 2 years ago

@sencagri Glad to hear! Thanks for reaching out and working it through with us.

udlose commented 2 years ago

Uninstalling all of the .NET 7 Preview releases resolved the issue for me

resting commented 2 years ago

Had the same problem on Macbook Arm64

What helped me:

  1. Remove VS 2022 for Mac
  2. Removing .net sdk and runtimes (https://learn.microsoft.com/en-gb/dotnet/core/additional-tools/uninstall-tool?tabs=macos and some manual scripts to remove .net 7 and dotnet folders in /etc and /usr/local/share folders)
  3. Install .net 7 and only after that step to install .net 6
  4. Intall VS for Mac.

Also i checked in Rider 2022.2 and 2022.3 EAP 7 and works fine there as well

ended up removing /usr/local/share/dotnet/sdk and /usr/local/share/dotnet/sdk-manifests. then reinstalled .net 7 followed by .net 6. was finally able to load the projects again with rider.

rodoUAM commented 2 years ago

I only unintall the NET CORE 7 preview from my PC and It works for me. I hope that It will be usefull

pplaissy commented 2 years ago

I have the same issue.

Fortunately, I have two computers running the same version of .NET 7.0 / Visual Studio 2022 with the same workloads. One works fine and the other is broken. I checked the path C:\Program Files\dotnet\sdk-manifests\7.0.100 and find that the PC with broken Visual Studio has an extra folder named microsoft.net.workload.mono.toolchain.

I deleted the extra folder, and now the .NET 7.0 / Visual Studio works fine.

image

The error message:

🤣:  dotnet new --help
Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException: 清单“wasm-tools”[microsoft.net.workload.mono.toolchain] 中的工作负载定义“C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain\WorkloadManifest.json”与清单“microsoft.net.workload.mono.toolchain.net7”[C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json] 冲突
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.ComposeWorkloadManifests()
   at Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadResolver.Create(IWorkloadManifestProvider manifestProvider, String dotnetRootPath, String sdkVersion, String userProfileDir)
   at Microsoft.DotNet.Workloads.Workload.List.WorkloadInfoHelper..ctor(VerbosityOptions verbosity, String targetSdkVersion, Nullable`1 verifySignatures, IReporter reporter, IWorkloadInstallationRecordRepository workloadRecordRepo, String currentSdkVersion, String dotnetDir, String userProfileDir, IWorkloadResolver workloadResolver)
   at Microsoft.DotNet.Cli.NewCommandParser.CreateHost(Boolean disableSdkTemplates, Boolean disableProjectContext, FileInfo projectPath, FileInfo outputPath, LogLevel logLevel)
   at Microsoft.DotNet.Cli.NewCommandParser.<GetCommand>g__GetEngineHost|11_0(ParseResult parseResult)
   at Microsoft.TemplateEngine.Cli.Commands.BaseCommand.CreateEnvironmentSettings(GlobalArgs args, ParseResult parseResult)
   at Microsoft.TemplateEngine.Cli.Commands.NewCommand.<CustomHelpLayout>b__31_0(HelpContext context)
   at Microsoft.DotNet.Cli.Parser.DotnetHelpBuilder.Write(HelpContext context)
   at System.CommandLine.Invocation.InvocationPipeline.GetExitCode(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<Invoke>g__FullInvocationChain|3_0(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.Invoke(IConsole console)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)

same issue, no projects could be loaded after the vs/net 7.0 update. Removing the microsoft.net.workload.mono.toolchain directory fixed it. Thank you very much 👍

MickCG commented 2 years ago

Deleting: C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain did the trick for me. I got so frustrated I deleted VS 2022, removed all the frameworks and no luck. A real pain worked like two days but removing that one directory did it. The fact that the install or update that MS created was not smart enough th do that kind of ticks me off, how stupid.

reecebradley commented 2 years ago

I don't have evident to prove it now but what it looked like to me from the CLI output was that .NET 7.0.100 was showing up as a preview. I uninstalled via add/remove programs - then installed via winget install --id Microsoft.DotNet.SDK.7

jkone27 commented 2 years ago

macos: in my case I had 7.0.1 preview, so i had to do this manually as dotnet uninstall tool wouldnt support uninstalling higher versions..

sudo rm -rf /usr/local/share/dotnet/sdk/7.0.100

this issue can happen if you previously installed preview or candidate versions, i had also to cleanup other folders for that related to -rc version of the same

DuckScapePhilip commented 2 years ago

None of these fixes have worked for me.

I had VS 2022 Preview installed before, but have since removed it. I have no preview version of .NET 7 installed, I have tried removing .NET 7 and re-installing. Nothing mentiond here has worked. I do not have this microsoft.net.workload.mono.toolchain folder.

image
DuckScapePhilip commented 2 years ago

My symptoms were:

  1. I could not build a .NET 6 MAUI app and debug on a physical android device after updating to .NET 7. Please note that I also did try with the emulator. However, I did not try to build and run to any other platform.

  2. My errors were:

    1>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Android is not installed. Please restore and try again.
1>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Maui.Core is not installed. Please restore and try again.
1>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Maui.Controls is not installed. Please restore and try again.
1>C:\Program Files\dotnet\sdk\7.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(376,5): error NETSDK1127: The targeting pack Microsoft.Maui.Essentials is not installed. Please restore and try again.

Strange enough, it seems somehow my SDK for Android API 31 somehow was either never installed or was uninstalled during the upgrade. I'm 99% sure it was installed because I have targeted that API for over 3 months now. Well, it turns out it wasn't, so I installed the API through the Android SDK manager, and now it works.

melytc commented 1 year ago

This happened to me too; deleting the preview sdk fixed it.

The error I was seeing:

D:\resource-explorer-prototype\src\ResourceExplorer.Tests\ResourceExplorer.Tests.csproj : error  : 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' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain\WorkloadManifest.json] 

conflicts with manifest 
'microsoft.net.workload.mono.toolchain.net7' [C:\Program Files\dotnet\sdk-manifests\7.0.100\microsoft.net.workload.mono.toolchain.net7\WorkloadManifest.json]