Start Debugging

Tag: aspnetcore

56 posts · Page 4 of 6

2026-06-09 blazor dotnet-11 aspnetcore

How to persist state across the Blazor static-to-interactive render boundary in .NET 11

A prerendered Blazor component runs its initialization twice and loses state at the interactive handoff. Fix it with the [PersistentState] attribute or the PersistentComponentState service in .NET 11.

2026-06-08 csharp dotnet dotnet-11

How to expose OpenAPI without Swashbuckle in ASP.NET Core 11

Swashbuckle is gone from the ASP.NET Core templates. Here is how to generate and serve an OpenAPI document in .NET 11 with the built-in Microsoft.AspNetCore.OpenApi package: AddOpenApi, MapOpenApi, transformers, multiple documents, build-time generation, and a UI on top.

2026-06-07 csharp dotnet dotnet-11

How to organize minimal API endpoints with MapGroup in ASP.NET Core 11

A complete guide to structuring minimal APIs in ASP.NET Core 11 with MapGroup: per-resource endpoint modules as extension methods, nested groups, shared filters and auth, route-parameter prefixes, OpenAPI tags, and the filter-ordering rules that surprise people.

2026-06-07 aspnetcore dotnet performance

How to use HybridCache in ASP.NET Core 11 with Redis as the L2 cache

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.

2026-06-07 csharp dotnet dotnet-11

How to validate request bodies in minimal APIs without controllers in ASP.NET Core 11

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.

2026-06-05 migration blazor dotnet

Migrate a Blazor Server app to Blazor United (Blazor Web App) in .NET 11

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.

2026-06-03 comparison dotnet aspnetcore

BackgroundService vs IHostedService vs Hangfire for background jobs in .NET 11

Pick BackgroundService for in-process loops, raw IHostedService when you need fine lifecycle control, and Hangfire when jobs must survive a restart. A decision matrix with code and the one gotcha that picks for you.

2026-05-31 csharp dotnet dotnet-11

How to run fire-and-forget work safely in ASP.NET Core with BackgroundService

Calling Task.Run from a controller loses work on shutdown, swallows exceptions, and captures disposed scoped services. The safe pattern is a bounded Channel queue drained by a BackgroundService that opens a fresh scope per work item and drains in-flight work on StopAsync.

2026-05-31 csharp dotnet dotnet-11

How to use scoped services inside a BackgroundService in ASP.NET Core 11

A BackgroundService is a singleton, so it cannot inject a scoped service like a DbContext directly. Take IServiceScopeFactory, open one scope per unit of work with CreateAsyncScope, resolve inside it, and dispose it when the work is done.

2026-05-26 comparison blazor dotnet

Blazor Server vs Blazor WebAssembly vs Blazor United in .NET 11: which should you pick in 2026?

For any new Blazor app on .NET 11, scaffold a Blazor Web App (the template formerly nicknamed Blazor United) and pick render modes per page. Server-only and WebAssembly-only templates only still make sense in narrow cases.