Shouldn't all wasm build tasks be put into one nuget package ?

@vargaz I thought MonoAOTCompiler could apply to iOS and Android as well

Shouldn't all wasm build tasks be put into one nuget package ?

This package is intended to be used beyond runtime. Each of the sdk's will define a workload that will contain a bunch of workload packs (the AOT MSBuild Task is one of them). That will allow the developer to choose (or not) to install different parts of the dotnet sdk.

I would prefer to have wasm specific tasks to be in their own package (should we need any).

We use the MonoAOTCompiler task in the mono samples, just not as NuPkg imports. The main purpose of making the NuPkg is for external use, so those developing outside of dotnet/runtime can call the MonoAOTCompiler task. Such as how https://github.com/dotnet/samples/tree/master/core/mono-samples are using the respective NuPkgs. Where would be the best place to note that?

We use the MonoAOTCompiler task in the mono samples, just not as NuPkg imports. The main purpose of making the NuPkg is for external use, so those developing outside of dotnet/runtime can call the MonoAOTCompiler task. Such as how https://github.com/dotnet/samples/tree/master/core/mono-samples are using the respective NuPkgs. Where would be the best place to note that?

Maybe in a README.md next to the pkgproj.

Have you tried using the generated nuget with such a sample?