Who contributed to .NET on July 8, 2026?

6 developers shipped this update, including EgorBo, LeafShi1, jakobbotsch, dotnet-maestro[bot], PureWeen, and Evangelink.

What were the notable .NET updates?

Remove FEATURE_BASICFREEZE, Fix SendKeys sequential immediate modifier(^a^c, +a+c, %f%t) parsing regression, and Remove concurrent verify_soh_segment_list call in background_sweep (#129873).

Jul 8, 2026

$ the-wire · showcase

RUNTIME CUTS DEAD CODE, WINFORMS FIXES SENDKEYS PARSING, MAUI TIGHTENS RELEASE TRACKING

By RepoJournal · Filed 06:04 UTC on July 8, 2026 · About .NET · Composed from the cited sources · methodology

6 people shipped this

dotnet-maestro[bot] @dotnet-maestro[bot] 2 cited

PureWeen @PureWeen 2 cited

Evangelink @Evangelink 2 cited

EgorBo @EgorBo 1 cited

LeafShi1 @LeafShi1 1 cited

jakobbotsch @jakobbotsch 1 cited

The runtime team removed years-old dead code paths while fixing a critical bug in WinForms keyboard input that broke sequential modifier sequences in migrated apps.

dotnet/runtime is cleaning house with FEATURE_BASICFREEZE removal [1], stripping out unconditionally-defined guards that haven't been disabled in production builds for years. This is parallel infrastructure work that pays off when shipping. Meanwhile, WinForms shipped a critical fix [2] for SendKeys sequential immediate modifier parsing (^a^c, +a+c, %f%t) that regressed when modifier state was refactored from reference to value tuple semantics without adding the ref keyword. Apps migrated from .NET Framework are hitting this in the field. The runtime also removed a concurrent GC verification call [3] that was firing false positives during background sweep when segment lists were actively mutating, plus landed thread state support [4] and task-returning thunk optimizations [5]. On the platform side, WPF and WinForms both pulled the latest VMR codeflow updates [6][7]. In MAUI and Copilot, the team is hardening release-readiness tracking with 3-hour refresh cadence [8], fixing the regression classifier that was misreporting closed issues as open-on-main [9], and across dotnet/skills, fixing agent hallucination in devops-health-check [10], sharpening skill activation routing [11], and making code-testing agents portable across Copilot CLI, Claude Code, and Gemini [12].

Action items

→ Review WinForms SendKeys fix if you maintain keyboard input logic or migrate F# apps dotnet/winforms [immediate]
→ Pull latest VMR codeflow updates into WPF and WinForms branches dotnet/wpf [plan]
→ Monitor MAUI release-readiness tracker for the 3h cadence bump and closed-issue fix dotnet/maui [monitor]
→ Test code-testing agents in Claude Code if you use multi-host Copilot deployments dotnet/skills [monitor]

References

[1] Remove FEATURE_BASICFREEZE ↗ dotnet/runtime
[2] Fix SendKeys sequential immediate modifier(^a^c, +a+c, %f%t) parsing regression ↗ dotnet/winforms
[3] Remove concurrent verify_soh_segment_list call in background_sweep (#129873) dotnet/runtime ↗
[4] [cDac] Implement thread state (#130029) dotnet/runtime ↗
[5] Skip save/restore of contexts in task-returning thunks; mark thunk infrastructure `NonVersionable` ↗ dotnet/runtime
[6] [main] Source code updates from dotnet/dotnet ↗ dotnet/winforms
[7] [main] Source code updates from dotnet/dotnet ↗ dotnet/wpf
[8] Keep release-readiness trackers fresh: 3h cadence, freshness banner, scoped event triggers ↗ dotnet/maui
[9] Never classify a CLOSED issue as open-on-main in release-readiness ↗ dotnet/maui
[10] fix: reinforce no-script-execution constraint in devops-health-check (#845) ↗ dotnet/skills
[11] Fix migrate-static-to-wrapper skill activation on evals ↗ dotnet/skills
[12] dotnet-test: make code-testing agent tools portable across Copilot CLI, Claude Code & Gemini CLI + add portability check ↗ dotnet/skills