workload wasi-experimental - is this where it's supported? Build tool issue on MacOS M1 - Error MSB4062 : Task could not be loaded from the assembly - WasmAppBuilder.dll.

[Simonl9l]

It seems dotnet workloads is an area of dotnet that is not, to many, well known about it seems. If this is the wrong place, please can you let me know?

I'm running on Apple Silicon (M1/Arm64).

I'm trying to use a project that is dependent on wasi-experimental and the wasi-sdk, and have followed the instruction to instal the MacOs (universal binaries).

It seem that if I follow all this correctly wasi-experimental is looking for the wasi-sdk in /Users/{profile}/.wasi-sdk/wasi-sdk-16.0 and, per the project maintainer, putting the bin, lib, share of the v20 sdk in this folder "works on Windows". I have installed v20 the same way.

I also have the WASI_SDK_PATH=/Users/{profile}/.wasi-sdk/wasi-sdk-16.0

If I try and build the project I get the following error:

0>Wasi.Sdk.targets(102,3): Error MSB4062 : The "Microsoft.WebAssembly.Build.Tasks.WasmResolveAssemblyDependencies" task could not be loaded from the assembly /usr/local/share/dotnet/packs/Microsoft.NET.Runtime.WebAssembly.Wasi.Sdk/8.0.2/Sdk/../tasks/net8.0/WasmAppBuilder.dll.  
Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
0>------- Finished building project: WasiInterfacePlugin. Succeeded: False. Errors: 1. Warnings: 0

Any clues, directions or hits are appreciated as this has me dead in the water.

[maraf]

It works with my setup

I have install wasi-experimental workload, downloaded (latest) WASI SDK and put it in /Users/marekfisera/Bin/wasi-sdk-21.0, then set WASI_SDK_PATH

export WASI_SDK_PATH=/Users/marekfisera/Bin/wasi-sdk-21.0

Now I can build an app generated from wasi-console template with native relink.

Can you do build in your environment and share a binlog (dotnet build -bl)?

[maraf]

I don't see the use of WasmResolveAssemblyDependencies in my build...

[Simonl9l]

@maraf thanks of replying please see attached.
msbuild.binlog.zip

Installed Workload Id      Manifest Version      Installation Source
--------------------------------------------------------------------
wasi-experimental          8.0.2/8.0.100         SDK 8.0.100        

[maraf]

The wasi-experimental workload is a successor of Wasi.Sdk package. Remove the package reference and things should work

[Simonl9l]

@maraf ah! Thanks for the spot observation, that was an experiment to fix my issue; but had not realized I'd left it in place. Removing that as you noted solved my issue.

Also if note I actually removed the was-idk install from /Users/{profile}/.wasi-sdk/wasi-sdk-16.0 and it still worked?

Does this mean that wasi-experimental includes its own wasi-sdk?

On the basis the workload is the successor to the sdk, is there any documentation on the wasi-experimental workload and what is supports etc ?

Now that it builds, I see that the build (for debug) produces a file structure that has a bin/net8.0/wasi-wasm/dotnet.wasm file. I was expecting the .wasm file to be named the same as the project?

Does this need additional project settings to name this as I need?

Thanks again - and apologies I may have created an issue due to my own error, so appreciate you help and observations.

[maraf]

No problem, I'm happy to help. The new workload has some rough edges.

Does this mean that wasi-experimental includes its own wasi-sdk?

Not yet. It's something that will most probably change, but at the moment you need to install wasi-sdk manually and set WASI_SDK_PATH to point to it.

On the basis the workload is the successor to the sdk, is there any documentation on the wasi-experimental workload and what is supports etc ?

These isn't any official documentation and we don't even have a list of supported MSBuild properties and items yet. You can read through build targets (please note that not everything mentioned in the comment in the linked file is working for wasi, as it's mostly copied from browser scenario) or ask questions around. We'll get better.

Now that it builds, I see that the build (for debug) produces a file structure that has a bin/net8.0/wasi-wasm/dotnet.wasm file. I was expecting the .wasm file to be named the same as the project?

The wasi build has two modes. Be default it produces a folder with separate files (dlls), in this mode the wasm file is dotnet.wasm, because it contains only .NET runtime. The other mode (WasmSingleFileBundle=true) bundles everything in a single wasm file and in this case the name of wasm file matches name of your project.