An error dialog pops up when creating the .Net Core project with the latest .NET SDK 6.0

[Zheng-Li01]

More info:

1. This is a regression issue, can't reproduce on .NET SDK 6.0.100-preview.5.21255.24-win-x64.
2. The issue can reproduce more types core project, such as winforms, wpf. console etc.

Version info:
NET SDK 6.0.100-preview.5.21257.10-win-x64.

Repro Steps:

1. Install the latest .Net 6.0 from https://github.com/dotnet/core-sdk.
2. Try to create .Net Core project.

Actual Results:
An error dialog pops up.

Expected Results:
Creating the .Net Core project with the latest .Net 6.0 successfully.

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.

[Zheng-Li01]

More info:
The project can be create/built/run successfully by using Command. However an error dialog pops up when trying to open it by using VS.

[davidfowl]

+1 nothing works after I upgrade

[dsplaisted]

@Zheng-Li01 What version of Visual Studio is this happening with?

[benaadams]

I get it in 16.10.0 Preview 2.1

[dsplaisted]

Can you try setting MSBuildEnableWorkloadResolver to false and see if that fixes the problems?

(You don't want to leave this permanently on, as it will disable any workloads, which in .NET 6 will include ios, android, and Blazor AOT support.)

[benaadams]

Nope

[dsplaisted]

@dotnet/templating-engine-maintainers @wli3 @marcpopMSFT This looks like it may be a separate issue from what #17536 is trying to fix. It looks like maybe the workload template resolver hasn't been updated to handle the manifest schema change. What's the process for updating that? Is it supposed to happen with normal .NET SDK insertions or what?

[DavidKarlas]

@phenning Where is logic for VS sync with optional workload templates, sounds like it needs updating?

[dsplaisted]

Specifically, I think that the template engine needs to use a version of the workload manifest reader with this change: #17329

[davidfowl]

If this requires a VS change to function, what does that mean for using nightly builds?

[dsplaisted]

I think it may mean you need to create projects from the command line.

You could also delete or rename the SDK manifests folder: C:\Program Files\dotnet\sdk-manifests. That would break iOS, Android, and Blazor AoT though.

[davidfowl]

So nobody can update the sdk? Can we turn off the workload thing by default until there's a version of vs that works ?