Enable wasm-tools workload for CoreCLR WASM targets#55324
Open
lewing wants to merge 1 commit into
Open
Conversation
Reflects dotnet/runtime#130380 in the Current (net11) Mono toolchain workload manifest: enables the wasm-tools workload to target CoreCLR browser-wasm. - WorkloadManifest.json.in: add the CoreCLR runtime pack (Microsoft.NETCore.App.Runtime.${NetVersion}.browser-wasm) to the wasm-tools pack list and define its framework alias to Microsoft.NETCore.App.Runtime.browser-wasm. - WorkloadManifest.targets.in: gate the Mono-specific imports (MonoAOTCompiler.Task and the browser-wasm MonoTargets/AOT.Cross ImportGroup) on UseMonoRuntime != false, and add a CoreCLR (UseMonoRuntime == false) ImportGroup that only pulls in the WebAssembly.Sdk. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 50e9f740-621e-480d-a9cf-ed0e572a995e
|
Azure Pipelines: Successfully started running 1 pipeline(s). 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Current (net11) Mono toolchain workload manifest in dotnet/sdk to mirror dotnet/runtime#130380, enabling the existing wasm-tools workload to support CoreCLR browser-wasm (in addition to Mono) by including the CoreCLR WASM runtime pack and conditionally importing Mono-vs-CoreCLR build logic.
Changes:
- Add the CoreCLR WASM runtime pack (
Microsoft.NETCore.App.Runtime.${NetVersion}.browser-wasm) to thewasm-toolsworkload and define it as aframeworkpack with analias-to. - Gate Mono-only MSBuild imports on
$(UseMonoRuntime) != 'false'and add a CoreCLR-specificbrowser-wasmImportGroup for$(UseMonoRuntime) == 'false'that imports onlyMicrosoft.NET.Runtime.WebAssembly.Sdk.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/Workloads/Manifests/Microsoft.NET.Workload.Mono.Toolchain.Current.Manifest/WorkloadManifest.targets.in | Gates Mono-only imports on UseMonoRuntime and adds a CoreCLR browser-wasm import path that only brings in WebAssembly.Sdk. |
| src/Workloads/Manifests/Microsoft.NET.Workload.Mono.Toolchain.Current.Manifest/WorkloadManifest.json.in | Adds the CoreCLR browser-wasm runtime pack to wasm-tools and defines the corresponding framework pack entry with an alias. |
akoeplinger
approved these changes
Jul 16, 2026
lewing
enabled auto-merge (squash)
July 16, 2026 20:53
Member
Author
|
@akoeplinger I don't understand what is going on with the helix monitor, it appears to just be stuck? |
maraf
approved these changes
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mirrors the workload manifest changes from dotnet/runtime#130380 into the SDK's copy of the Current (net11) Mono toolchain workload manifest. This enables the existing
wasm-toolsworkload to target CoreCLRbrowser-wasm, in addition to Mono, by including the CoreCLR WASM runtime pack.The workload manifests are authored in this repo under
src/Workloads/Manifests/. The runtime PR changed the equivalent.intemplates on its side; this PR reflects those same changes here so the shipped manifest stays in sync.Changes
src/Workloads/Manifests/Microsoft.NET.Workload.Mono.Toolchain.Current.Manifest/:Microsoft.NETCore.App.Runtime.${NetVersion}.browser-wasm(the CoreCLR runtime pack) to thewasm-toolsworkload's pack list.frameworkpack definition aliasing toMicrosoft.NETCore.App.Runtime.browser-wasm.'$(UseMonoRuntime)' != 'false':MonoAOTCompiler.Taskimport, andbrowser-wasmImportGroup that pulls inMonoTargets.Sdkand theAOT.Crosspack.'$(UseMonoRuntime)' == 'false')browser-wasmImportGroup that only imports theWebAssembly.Sdk(build targets + Emscripten). The CoreCLR runtime pack and crossgen2 are resolved by the SDK via its ownKnownRuntimePack/KnownCrossgen2Pack, so noMonoTargets.Sdk,MonoAOTCompiler, orAOT.Crosspack is needed.Notes
main.${RuntimeVersion}convention (resolving to the runtime pack package version) rather than runtime's${PackageVersion}, consistent with the surrounding Mono framework pack entries.Related