cck-dependency-injection

To fix a captive dependency in .NET dependency injection, resolve lifetime mismatches where a singleton service captures a scoped service. Refactoring service registrations ensures correct lifetimes and prevents memory leaks.

The best way to register decorators with Scrutor in .NET is using convention-based registration to safely select implementations. This composition pattern ensures correct service lifetimes and prevents stale data in production.

You can use keyed services in .NET 8 to select specific implementations during dependency injection registration. This composition pattern allows safe resolution of multiple service variants without causing lifetime conflicts.

A singleton cache captures a scoped DbContext because dependency injection lifetime mismatches force the scoped service to live as long as the singleton. Correcting service registrations prevents this captive dependency and memory leak.

Yes, you can use factory delegates for dependency injection in .NET backend services to safely construct implementations. This pattern supports correct service lifetimes and prevents captive dependency anti-patterns.

Yes, this dependency injection guidance applies to backend services and libraries targeting .NET 8 through .NET 10. It ensures correct service lifetimes and safe registration patterns across these framework versions.