unity-di

Configure Unity DI by registering types with configurable lifetimes and integrating per-request scoping via hierarchical lifetime management for ASP.NET MVC 5 and Web API 2 projects. This ensures proper container resolution and dependency injection across controllers.

Per-request scope lifetime management in Unity DI uses hierarchical lifetime management to ensure resolved dependencies are scoped to a single HTTP request. This prevents shared state issues and ensures proper disposal of scoped services in ASP.NET applications.

Unity DI supports registration by convention to map interfaces to implementations automatically, alongside named registrations for resolving multiple implementations of the same interface. This reduces boilerplate configuration and ensures testability across large codebases.

Yes, Unity DI supports both constructor and property injection patterns in .NET Framework apps. Constructor injection is used for required dependencies while property injection handles optional dependencies, with configurable lifetimes managing resolution behavior.

Common Unity DI pitfalls include incorrect lifetime management causing captive dependencies, missing per-request scoping in ASP.NET, and improper registration-by-convention setups. Following consolidated patterns for container setup and registration prevents misconfigurations and ensures testability.

Unity DI per-request lifetime resolution failures in Web API 2 typically stem from missing hierarchical lifetime management configuration or improper container setup. Ensuring correct per-request scoping integration and proper registration of dependencies across the dependency chain resolves these issues.