RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Pick a date

  1. Sat 16 may
  2. Sun 17 may
  3. Tue 19 may
  4. Wed 20 may
  5. Thu 21 may
  6. Sat 23 may
  7. Sun 24 may
  8. Mon 25 may
  9. Tue 26 may
  10. Wed 27 may
  11. Thu 28 may
  12. Fri 29 may
  13. Sat 30 may
  14. Sun 31 may
  15. Mon 1 jun
  16. Mon 8 jun
  17. Tue 9 jun
  18. Today 10 jun

The Wire · Showcase

ROSLYN AND RUNTIME FLOW INTO MAIN AS SDK FIXES TEST COMMAND PARSING

By RepoJournal · Filed · About .NET

The compiler and runtime teams shipped major codeflow updates overnight while the SDK addressed a critical CLI parser crash that blocks all dotnet commands when global.json is unreadable.

Roslyn, runtime, and MSBuild all synchronized with the main dotnet repository [1] [2] [3], bringing compiler refinements and runtime JIT optimizations into the release pipeline. The SDK team shipped two high-impact fixes: a parser robustness improvement that prevents total CLI lockout when global.json fails to load [4], and a terminal logger argument fix that now correctly routes `--tl:off` flags to MSBuild instead of the test runner [5]. In the runtime layer, JIT loop cloning got more flexible to handle additional statement patterns [9], while async callable task thunks received a continuation caching optimization that trims binary size by over 214KB in NAOT builds [10]. The .NET 11.0.1xx-preview5 build table landed [6], signaling the next preview cycle is locked in. ASP.NET Core also refined its CI infrastructure with 1ES pipeline consolidation for component E2E tests [7] and triage agent improvements [8].

Action items

References

  1. [1] [main] Source code updates from dotnet/roslyn ↗ dotnet/dotnet
  2. [2] [main] Source code updates from dotnet/runtime ↗ dotnet/dotnet
  3. [3] [main] Source code updates from dotnet/msbuild ↗ dotnet/dotnet
  4. [4] Don't crash the CLI parser when global.json is unreadable ↗ dotnet/sdk
  5. [5] Forward terminal logger arguments to MSBuild during `dotnet test` ↗ dotnet/sdk
  6. [6] Update build table to 11.0.1xx-preview5 ↗ dotnet/dotnet
  7. [7] Add 1ES Unofficial pipeline for Components E2E tests ↗ dotnet/aspnetcore
  8. [8] Update triage agent to separate label and type instructions ↗ dotnet/aspnetcore
  9. [9] JIT: generalize cloning conditions slightly ↗ dotnet/runtime
  10. [10] Cache continuation used for runtime async callable task thunks ↗ dotnet/runtime

FAQ

What changed in .NET on May 27, 2026?
The compiler and runtime teams shipped major codeflow updates overnight while the SDK addressed a critical CLI parser crash that blocks all dotnet commands when global.json is unreadable.
What should .NET teams do about it?
Test the global.json parser fix immediately if you maintain build systems or CI pipelines • Verify terminal logger switches work correctly in dotnet test after the next SDK build • Monitor the 11.0.1xx-preview5 cycle for breaking changes in Roslyn and runtime
Which .NET repositories shipped on May 27, 2026?
dotnet/dotnet, dotnet/sdk, dotnet/aspnetcore, dotnet/runtime

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.