Missing workload check causes error for WasmLinkerTest project

[mthalman]

When using the most recent build of .NET 8 RC1 SDK to build the aspnetcore repo, the following error occurs:

/vmr/.dotnet/sdk/8.0.100-rc.1.23381.1/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To build this project, the following workloads must be installed: wasm-tools [/vmr/src/aspnetcore/artifacts/source-build/self/src/src/Components/WebAssembly/testassets/WasmLinkerTest/WasmLinkerTest.csproj]
/vmr/.dotnet/sdk/8.0.100-rc.1.23381.1/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To install these workloads, run the following command: dotnet workload restore [/vmr/src/aspnetcore/artifacts/source-build/self/src/src/Components/WebAssembly/testassets/WasmLinkerTest/WasmLinkerTest.csproj]

This is a recent regression that I believe is caused by the change in dotnet/emsdk#381.

This was caught by a build scenario for source-build which builds the SDK from the VMR and then uses that output SDK to build the VMR again. Since the input to the first build is currently the RC1 sources, we're using the RC1 SDK to build the VMR. It then fails in that second build when building the aspnetcore repo. This regression occurred between these commits: https://github.com/dotnet/dotnet/compare/c536f689..77cd3567, which contains the changes from dotnet/emsdk#381.

This failure occurs in the _CheckForMissingWorload target. Prior to this regression, the build would skip that target because @(MissingWorkloadPack) was empty. But now it is set with the following content:

MissingWorkloadPack
    Microsoft.NET.Runtime.Emscripten.Node
        Version = 8.0.0-rc.1.23377.1
    Microsoft.NET.Runtime.Emscripten.Sdk
        Version = 8.0.0-rc.1.23377.1
    Microsoft.NET.Runtime.Emscripten.Cache
        Version = 8.0.0-rc.1.23377.1
    Microsoft.NET.Runtime.Emscripten.Cache
        Version = 8.0.0-rc.1.23377.1

We've got three repos involved here so it's not clear to me what needs to be addressed:

• Is all of this expected and aspnetcore needs to adjust the build configuration to account for this?
• Is there an issue with how Allow WebAssembly SDK without workload emsdk#381 is implemented?
• Is the sdk implementation of the missing workload check flawed in some way?

cc @dsplaisted, @maraf

[dsplaisted]

@lewing @steveisok @joeloff @marcpopMSFT

[mthalman]

This is fixed by #49761.