The interesting .NET news this month is the boring news

Two .NET stories crossed my feed this month. One is loud, one is quiet, and I keep clicking the quiet one.

The loud story is .NET 11 Preview 6. The headline is that MAUI mobile apps, on Android, iOS, and Mac Catalyst, now run on CoreCLR only; Mono is gone from that path. That is a real consolidation, one runtime instead of two, and it will matter to anyone shipping phone apps. It does not touch me. I ship a web app in a Linux container, so I read it, nodded, and moved on.

The quiet story is the July 14 servicing release: .NET 10.0.10, 9.0.18, and 8.0.29, closing 17 CVEs across the three supported lines. No new syntax, no demo, nothing to tweet. Just a pile of security fixes for the runtime that everything else sits on.

I clicked that one because this blog is downstream of it. blogfor.net is a small .NET 10 app in a container (here is how that works). "Patch .NET" for me is not a package bump, it is rebuild the image against the new base layer and redeploy. So a boring servicing note is really a to-do item with my name on it.

Here is the part I have to argue with myself about. The preview is where the fun is, the servicing release is where the risk is, and I spend more attention on the fun. C# 14 already shipped with .NET 10 last fall as the LTS language, and I have happily played with its new toys. I have been much slower to treat "17 CVEs, update today" as the actual work. The vendor is telling me plainly which one is urgent, and it is not the one with the changelog I enjoy reading.

So this week the unglamorous thing wins. Rebuild the container, take the patched runtime, ship it. The new language features can wait for a preview I actually have time to enjoy.