Start Debugging

Tag: dependency-injection

12 posts · Page 1 of 2

2026-09-21 aspire kafka dotnet

Aspire 13.5.4 Stops Kafka Health Checks From Leaking a Producer on Every Probe

Before Aspire 13.5.4, every AppHost health check on an AddKafka resource created a new Confluent producer that nobody disposed, so polling threads piled up and the AppHost burned CPU. The fix, and the HealthCheckRegistration.Factory trap behind it, applies to your own health checks too.

2026-08-16 csharp dotnet dotnet-11

How to use IDbContextFactory<T> from a singleton service in Blazor

A singleton cannot inject a DbContext, but it can inject IDbContextFactory<T>, because AddDbContextFactory registers the factory as a singleton by default. Create and dispose one context per call, never cache the instance.

2026-08-03 csharp dotnet dotnet-11

How to validate options at startup with IValidateOptions<T> in .NET 11

Implement IValidateOptions<T>, register it in DI, and chain ValidateOnStart so a bad appsettings.json kills the process instead of the first request that touches it. Covers the .NET 11 Validate<TValidator>() overload, async validation through IAsyncValidateOptions<T>, and the three places ValidateOnStart silently does nothing.

2026-08-01 comparison csharp dotnet

IOptions<T> vs IOptionsSnapshot<T> vs IOptionsMonitor<T> in .NET 11

Default to IOptions<T>. Use IOptionsMonitor<T> when a singleton has to see config reloads, and IOptionsSnapshot<T> only when a scoped consumer wants a value that is stable for one request. The deciding axis is the lifetime of the consumer, not the shape of the settings.

2026-06-26 errors csharp dotnet

Fix: No service for type 'Microsoft.EntityFrameworkCore.DbContextOptions' has been registered

EF Core throws this when AddDbContext never ran, ran after Build, or your context's constructor takes the wrong DbContextOptions. Register before Build and use DbContextOptions<YourContext>.

2026-06-23 csharp dotnet dotnet-11

How to register and resolve keyed services in .NET 11 dependency injection

Register more than one implementation of the same interface under a key with AddKeyedSingleton/Scoped/Transient, then resolve them with [FromKeyedServices], GetRequiredKeyedService, or KeyedService.AnyKey. The keyed and non-keyed registries are separate, which is the gotcha that bites most people.

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-30 migration mediatr dependency-injection

Migrate from MediatR to plain dependency injection in .NET 11

A step-by-step checklist to remove MediatR 12-14 and replace IRequest handlers, ISender, pipeline behaviors, and INotification with plain service classes and constructor injection.

2026-05-23 comparison mediatr dependency-injection

MediatR vs plain service classes in 2026: should the license change move you?

For new code, plain service classes are the better default. MediatR's July 2025 license change matters only if you sit above the $5M Community threshold or refuse the RPL-1.5 copyleft. Keep MediatR when pipeline behaviors are load-bearing.

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.