Who contributed to .NET on June 11, 2026?

6 developers shipped this update, including kubaflo, PureWeen, github-actions[bot], lewing, paulmedynski, and LeafShi1.

What were the notable .NET updates?

11.0.0-preview.5.26304.4, Fix /review tests comment formatting, and Improve code-review skill with regression prevention safeguards.

Jun 11, 2026

$ the-wire · showcase

MAUI 11 PREVIEW 5 SHIPS WITH REGRESSION SAFEGUARDS, BLAZOR WASM 404S FIXED IN SDK

By RepoJournal · Filed 06:05 UTC on June 11, 2026 · About .NET · Composed from the cited sources · methodology

6 people shipped this

kubaflo @kubaflo 1 cited

PureWeen @PureWeen 1 cited

github-actions[bot] @github-actions[bot] 1 cited

lewing @lewing 1 cited

paulmedynski @paulmedynski 1 cited

LeafShi1 @LeafShi1 1 cited

Microsoft.NET.Workloads 11.0.100-preview.5 is live, but the real story is the systematic fixes shipping across the stack: MAUI locked down code review invariants from 372+ regressions, while SDK 10.0.4xx solves a critical Blazor WebAssembly bootstrap failure that was breaking every .NET 11 preview 6 build.

MAUI 11.0.0-preview.5 dropped its workload bundle [1] with companion tooling updates that stabilize the cross-platform story. The team isn't just shipping features; they're instrumenting the review process itself. Two structural changes landed in parallel: the `/review tests` comment formatter now surfaces failures more clearly [2], and the code-review skill itself gained four process invariants [3] distilled from systematic analysis of historical regressions. This is the kind of infrastructure investment that prevents the next wave of bugs before they ship. Over in SDK land, the 10.0.4xx branch merged from release [4], but the critical fix lives in an upstream PR addressing a Blazor WebAssembly disaster [5]. Apps built with the .NET 11 preview 6 SDK band were getting HTTP 404s on `blazor.webassembly.js` at boot time, which meant Blazor never started. Root cause: materialized framework assets weren't clearing asset groups properly, causing a fingerprinting mismatch. This one shipped broken and has now shipped fixed. In SqlClient, version range pinning landed [6] to prevent NuGet from silently resolving incompatible sibling packages at restore time. The approach is surgical: derive upper-bound ranges from centralized `Directory.Packages.props`, apply `[floor, ceiling)` semantics, and let MSBuild handle the math. WinForms also landed a focus-handling fix [7] that restores modal menu tracking for ToolStripDropDown scenarios that got regressed by a tighter focus guard in the previous sprint.

Action items

→ Update MAUI workloads to 11.0.100-preview.5.26309.3, verify Xcode 26.5 and JDK 21.0.8 are present dotnet/maui [plan]
→ If shipping Blazor WebAssembly on .NET 11 preview 6 SDK, pull the asset group fix immediately from dotnet/sdk main dotnet/sdk [immediate]
→ Audit SqlClient dependencies: apply upper-bound version ranges from Directory.Packages.props to prevent restore-time resolution drift dotnet/SqlClient [plan]
→ Test WinForms SmartTag and DropDown scenarios if you shipped the previous focus-handling change dotnet/winforms [monitor]

References

[1] 11.0.0-preview.5.26304.4 ↗ dotnet/maui
[2] Fix /review tests comment formatting ↗ dotnet/maui
[3] Improve code-review skill with regression prevention safeguards ↗ dotnet/maui
[4] [automated] Merge branch 'release/10.0.4xx' => 'main' ↗ dotnet/sdk
[5] [StaticWebAssets] Clear AssetGroups when materializing framework assets (fixes Blazor WASM blazor.webassembly.js 404) ↗ dotnet/sdk
[6] Use upper-bound version ranges for sibling package dependencies ↗ dotnet/SqlClient
[7] Fix the focus issue of SmartTag/DropDown by preserving the modal menu tracking of ToolStripDropDown. ↗ dotnet/winforms