Blog

Wire HybridCache to a Redis L2 in ASP.NET Core 11: register the service, add the StackExchange Redis distributed cache, and let GetOrCreateAsync give you a two-tier cache with built-in stampede protection and tag invalidation.

ASP.NET Core 11 has built-in validation for minimal APIs: call AddValidation, annotate your request record with DataAnnotations, and a source generator validates the bound model and returns 400 ProblemDetails before your handler runs. No controllers, no FluentValidation, no manual checks.

.NET 11 Preview 4 ships a built-in meter for Microsoft.Extensions.Caching.Memory, so cache hit ratio and evictions flow into OpenTelemetry without a background poller.

For a new .NET agent in 2026, start on Microsoft Agent Framework 1.0. Semantic Kernel is in maintenance mode. Here is the side-by-side and the one case where SK still wins.

A step-by-step migration from the old Startup.cs plus WebHostBuilder hosting model to the minimal hosting model with WebApplication.CreateBuilder, including the ASPDEPR008 deprecation, middleware ordering, IStartupFilter, and how to keep your tests working.

A practical migration from the ASP.NET Framework System.Web.HttpContext to the ASP.NET Core 11 HttpContext: HttpContext.Current, the property map, Server.MapPath, Session, and the System.Web adapters shim for incremental migrations.

A practical checklist for reverting ValueTask and ValueTask<T> return types to Task and Task<T>, what breaks at the call sites, how to verify each change, and how to know whether the swap was ever worth it.

Anthropic is splitting programmatic Claude usage off your subscription on 2026-06-15. Here is what counts as programmatic, the per-plan credit, and how to keep your CI agents from silently stalling.

All three hit 1.0. Pick Microsoft Agent Framework if you live in Azure and .NET, LangChain/LangGraph for vendor-neutral graph orchestration, LlamaIndex for retrieval-grounded agents.

A step-by-step checklist to move a standalone Blazor Server app to the unified Blazor Web App template on .NET 11, keeping every page on InteractiveServer with zero behaviour change.