Skip to content

[wasm] Remove "UsingBlazorOrWasmSdk" condition from emscripten workload detection#52600

Merged
maraf merged 2 commits intomainfrom
EmscriptenUsingBlazorOrWasmSdk
Jan 22, 2026
Merged

[wasm] Remove "UsingBlazorOrWasmSdk" condition from emscripten workload detection#52600
maraf merged 2 commits intomainfrom
EmscriptenUsingBlazorOrWasmSdk

Conversation

@maraf
Copy link
Copy Markdown
Member

@maraf maraf commented Jan 21, 2026

@maraf maraf added this to the 11.0.1xx milestone Jan 21, 2026
@maraf maraf requested review from akoeplinger and lewing January 21, 2026 09:09
@maraf maraf self-assigned this Jan 21, 2026
Copilot AI review requested due to automatic review settings January 21, 2026 09:09
@maraf maraf enabled auto-merge (squash) January 21, 2026 09:10
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the Blazor/WebAssembly SDK condition from Emscripten workload detection logic, syncing with runtime changes that enable browser-wasm library mode without requiring the workload. This is a companion change to PR #52250 which made a similar update to the Mono.Toolchain manifest.

Changes:

  • Simplified the UsingBrowserRuntimeWorkload condition to only require the workload when AOT compilation is explicitly enabled, removing the check that forced workload usage for non-Blazor/WebAssembly SDK scenarios
  • Added a guard to prevent overriding previously set UsingBrowserRuntimeWorkload values

@maraf maraf merged commit b3cc731 into main Jan 22, 2026
26 checks passed
@maraf maraf deleted the EmscriptenUsingBlazorOrWasmSdk branch January 22, 2026 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants