Closed pkanavos closed 3 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.
Yes, we renamed the workload manifests which causes issues when you have both installed. This is covered in the known issues here: https://github.com/dotnet/core/blob/main/release-notes/6.0/known-issues.md#preview-5
@dsplaisted this probably needs a stronger warning then - probably in the blg posts themselves. This breaks dotnet
right from the start for people that had Preview 4 installed in a completely unexpected way, even if they never used workloads.
Kind of like Eddie Murphy in Best Defence:
"The WAM's overheating! The WAM's overheating! What the hell is a WAM!?!"
We've now released workarounds for this in all VS and recent previews so this specific issue should no longer be a blocker.
After installing .NET 6 Preview 5, executing
dotnet new
ordotnet workload list
on a machine that had Preview 4 installed throws:The
/usr/local/share/dotnet/sdk-manifests/6.0.100
folder seems to have manifests for the same workloads with different names, eg an oldMicrosoft.NET.Workload.MacCatalyst
and a newermicrosoft.net.sdk.maccatalyst
, with a workload id `"microsoft-maccatalyst-sdk-full":Removing Preview 4 using the script in Uninstall .NET doesn't help.
Possible workaround
Manually removing all
Microsoft.NET.Workload.*
folders allowsdotnet new
anddotnet workload list
to run, but the latter’s result is an empty list.The contents of the manifest folder after cleanup are :
Creating a new project, eg a Blazor Wasm project, works even though the
Microsoft.NET.Workload.BlazorWebAssembly
folder was deleted:dotnet info
dotnet --info
returns :