Start Debugging

Tag: aspnetcore

80 posts · Page 7 of 8

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.

2026-05-24 dotnet-11 aspnetcore openapi

ASP.NET Core in .NET 11 Preview 4 Teaches OpenAPI About the HTTP QUERY Method

.NET 11 Preview 4 makes ASP.NET Core OpenAPI generation recognize HTTP QUERY as a first-class operation in OpenAPI 3.2, with a graceful fallback for 3.0 and 3.1 documents.

2026-05-21 comparison aspnetcore minimal-apis

Minimal APIs vs controllers in ASP.NET Core 11: which should you pick in 2026?

Pick minimal APIs by default in ASP.NET Core 11. Use controllers only when you need MVC features that minimal APIs still do not match: convention-based routing across many actions, MVC-style filters, or Razor views.

2026-05-12 errors csharp dotnet

Fix: InvalidOperationException: Synchronous operations are disallowed

Replace the Stream.Read or Write call with ReadAsync/WriteAsync. As a last resort, set AllowSynchronousIO on Kestrel, IIS, or per-request via IHttpBodyControlFeature.

2026-05-10 errors csharp dotnet

Fix: Cannot consume scoped service 'X' from singleton 'Y'

ASP.NET Core's scope validation throws this when a singleton would capture a scoped dependency for the rest of the process. Make the consumer scoped, or take IServiceScopeFactory and create a scope on demand.

2026-05-10 errors csharp dotnet

Fix: Unable to resolve service for type 'X' while attempting to activate 'Y'

ASP.NET Core throws this when a constructor asks for a type that was never registered, was registered on the wrong container, or was added after the host was built. Three concrete fixes cover almost every case.

2026-05-05 errors csharp dotnet

Fix: System.InvalidOperationException: No connection string named 'DefaultConnection' could be found

If GetConnectionString returns null in .NET 11, your appsettings.json is missing the key, not copied to the build output, or the wrong environment file is being selected. Three checks fix 95% of cases.