DependencyInjection.Lifetime.Analyzers

DI003

Captive Dependency

singleton services capturing scoped or transient dependencies, including constructor injection, `IEnumerable<T>` collection captures, known scoped framework services such as `IOptionsSnapshot<T>`, EF Core contexts and `DbContextOptions<TContext>` registrations from `AddDbContext(...)`, `AddDbContextFactory(...)`, `AddDbContextPool(...)`, and `AddPooledDbContextFactory(...)` including service/implementation overload self-registrations, and high-confidence factory paths such as inline delegates, stable local delegate factories, method-group factories, `GetServices<T>()`, keyed resolutions, and `ActivatorUtilities.CreateInstance(...)` without explicit constructor arguments.

Severity: Warning · Code fix: Yes

DI015

Unresolvable Dependency

registered services with direct or transitive constructor/factory dependencies that are not registered (including keyed and open-generic paths).

Severity: Warning · Code fix: Yes

DI016

BuildServiceProvider Misuse

`BuildServiceProvider()` calls while composing registrations (for example in `ConfigureServices`, `IServiceCollection` extension registration methods, registration lambdas, or builder-style `.Services` helper flows).

Severity: Warning · Code fix: No

DI007

Service Locator Anti-Pattern

resolving dependencies via `IServiceProvider` inside app logic.

Severity: Info · Code fix: No

DI001

Service Scope Not Disposed

`IServiceScope` instances created with `CreateScope()` or `CreateAsyncScope()` that are never disposed, including scopes whose only disposal call is hidden behind a conditional branch, switch section, loop, catch block, or after a branch exit that can bypass shared cleanup. DI001 recognizes predeclared nullable scope locals assigned conditionally when a later conditional-access, non-null-guarded, same-branch pre-exit, or `finally` disposal reliably closes ownership, while still reporting reassignment leaks and loop-created scopes that need per-iteration disposal.

Severity: Warning · Code fix: Yes

DI014

Root Service Provider Not Disposed

root providers from `BuildServiceProvider()` that are never disposed, including local providers whose only manual disposal is conditional, catch-only, after reassignment to another provider, or after repeated creation inside a loop.

Severity: Warning · Code fix: Yes

Problem guide

Fix ObjectDisposedException From Scoped Services

These diagnostics catch the most common scope-lifetime mistakes that lead to disposed-service failures in background jobs, middleware, and startup code.

Problem guide

Find Captive Dependencies In ASP.NET Core

This page is for teams searching for captive dependency detection in ASP.NET Core, worker services, and generic-host apps.

Problem guide

Avoid BuildServiceProvider In ConfigureServices

Use these rules when you want to stop BuildServiceProvider misuse during registration while still allowing intentional provider factory methods.

Problem guide

Catch Unable To Resolve Service For Type Failures Earlier

These diagnostics focus on missing registrations, factory paths, keyed lookups, and incompatible implementation types.

Problem guide

Reduce IServiceProvider Injection And Service Locator Usage

Use these diagnostics when you want a stronger constructor-injection culture across app code and shared libraries.

Problem guide

Catch Disposable Transient Service Registrations

This rule is useful when teams are diagnosing resource leaks caused by transient disposables that look harmless in reviews.

Problem guide

Spot Constructor Over-Injection Early

This rule is intentionally softer than runtime-failure diagnostics, but it is useful for preventing DI-heavy classes from becoming maintenance hotspots.

Problem guide

Detect TryAdd And Duplicate Registration Misuse

This page targets teams debugging confusing registration order issues and silent overrides in service composition code.

Problem guide

Use CreateAsyncScope In Async Methods

Use this rule when background services, async handlers, or hosted-service workflows are mixing sync scopes into async disposal paths.