dependency-injection

Dependency injection fails because singletons live longer than scoped services, creating a captive dependency bug. You must prevent singleton/scoped mismatches by selecting appropriate service lifetimes and ensuring safe singleton behavior with scoped dependencies.

In dependency injection, AddScoped creates one instance per request, AddTransient creates a new instance every time, and AddSingleton creates a single shared instance. Accurate lifetime selection prevents common service registration errors and improves maintainability.

Keyed services in dependency injection allow strategy-style resolution by registering services with distinct keys. You resolve the desired implementation at runtime by specifying the key, enabling clean composition and flexible service wiring without complex factory delegates.

You apply the decorator pattern in dependency injection by wrapping an existing service registration to handle cross-cutting concerns. This keeps implementations swappable and testable while structuring cross-cutting behavior cleanly through composition.

Yes, Scrutor enables convention-based dependency injection wiring in .NET applications. It automatically registers interfaces and implementations by convention, keeping service registration clean and reducing manual configuration errors.

Use factory delegates in dependency injection when you need runtime provider selection or dynamic service resolution. While constructor injection is the default, factories provide flexibility for complex wiring scenarios where the implementation is determined at runtime.