LoginSign Up
← Back to all sparks
A

ASP.NET Core

DEVOPS
Velocity5.0

Cross-platform framework for building modern cloud-based web applications

asp.net ↗

Three supported branches, monthly servicing, and no directional change in sight

servicingmulti-branchblazordependency-flowpreview-train
◆Current state
ASP.NET Core is running a disciplined servicing operation across .NET 8, 9 and 10 simultaneously, cutting patch releases on all three in the same window, while .NET 11 moves through numbered previews. The content is what servicing looks like: branding bumps, dependency flows from dotnet/arcade and dotnet/dotnet, submodule updates, and a thin layer of genuine fixes. Blazor is where most of the real repairs land — component disposal behaviour, Virtualize null references, WASM HTTPS startup.
◆Where it's heading
This is a maturity plateau rather than a slowdown. The team's visible effort is going into keeping three LTS-era branches synchronized and safe, with new capability confined to the .NET 11 preview lane where it is not yet visible in these notes. Performance and reliability fixes cluster around cold-start paths and Blazor, suggesting those are where production pain reports concentrate.
◆Prediction
Expect the same three-branch patch cadence to continue on a monthly rhythm, with the next substantive news arriving in a .NET 11 preview rather than in any 8/9/10 servicing release.

◆Recent moves

  1. 19d ago

    Blazor disposal and Virtualize fixes in the .NET 10 patch

    The most substantive servicing release in this window: OwningComponentBase regains its original Dispose behaviour, Virtualize stops throwing null references, and KeyRingProvider no longer starves the thread pool on cold start. Real production-pain fixes rather than the dependency churn that fills most of these notes.

    View source ↗
  2. 19d ago

    Routine .NET 9 servicing: branding and dependency bumps

    Branding to 9.0.18, arcade and extensions dependency flows, npm updates, and internal commit merges. Nothing user-visible, which is exactly the point of a servicing release on a stable branch.

    View source ↗
  3. 19d ago

    Routine .NET 8 servicing: branding and dependency bumps

    The .NET 8 twin of the same servicing pass, cut in the same window with the same shape of content. Publishing all three branches together is the operational signature of this project.

    View source ↗
  4. 1mo ago

    Preview 6 build fixes Blazor WASM standalone HTTPS

    A single-fix preview build on the .NET 11 line, repairing standalone Blazor WASM HTTPS startup. It sits in the preview lane where .NET 11's actual feature work is happening, but this particular build carries none of it.

    View source ↗
  5. 1mo ago

    Antiforgery token preservation and disconnect handling in .NET 10

    Preserving the antiforgery token and detaching methods only once disconnection is confirmed are both correctness fixes in the interactive-component path, the same Blazor surface that dominates the later patch as well.

    View source ↗
  6. 1mo ago

    Minimal .NET 9 patch: dependency flow only

    One of the thinnest releases in the window — branding and two dependency flows from arcade and extensions. Worth noting mainly as evidence of how mechanical the servicing rhythm has become on the stable branches.

    View source ↗