Skip to content

fix(codec): make Browser runtime identity deterministic - #705

Merged
SunSi12138 merged 4 commits into
devfrom
fix/browser-runtime-family-identity-20260918
Sep 18, 2026
Merged

SunSi12138 merged 4 commits into
devfrom
fix/browser-runtime-family-identity-20260918

Conversation

@SunSi12138

Copy link
Copy Markdown
Owner

Follow-up to #704.

Release Gate #607 proved the Browser CoreCLR probe publishes and runs successfully under .NET 11 RC1, but also exposed that Type.GetType("Mono.Runtime") is not a reliable Browser/WASM discriminator: the existing .NET 10 Mono Browser probe returned null and was misclassified as CoreCLR.

Use the actual Browser probe build selection instead:

  • default/net10 Browser build records Mono with platform-runtime-pack provenance;
  • the SHARPLINK_BROWSER_CORECLR / UseMonoRuntime=false build records CoreCLR with build-runtime-selection provenance.

The runtime still records and validates observed TFM, RID, pointer size, framework/runtime version, SDK version, endianness, and compilation mode. This removes the unreliable reflection inference without weakening compatibility semantics.

@SunSi12138
SunSi12138 merged commit 400f490 into dev Sep 18, 2026
14 checks passed
@SunSi12138
SunSi12138 deleted the fix/browser-runtime-family-identity-20260918 branch September 18, 2026 11:27
SunSi12138 added a commit that referenced this pull request Sep 18, 2026
Advance the main synchronization branch to the current dev tree after #705.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant