dependency-injection-patterns

Organize dependency injection registrations by grouping related services into feature-specific Add* extension methods, reducing oversized Program.cs files and enabling test-time composition. Call these modular extensions hierarchically to compose your application's service collection.

Modularize ASP.NET Core service collections by creating feature-based Add* extension methods that encapsulate service registrations. This pattern enables test-time reuse by allowing tests to compose only the specific feature services needed without loading the entire application's dependency graph.

Yes, this dependency injection pattern supports advanced ASP.NET Core features including keyed services and options configuration. The extension method approach accommodates these modern Microsoft.Extensions.DependencyInjection capabilities within feature-specific registration groups.

Yes, feature-based Add* extension methods work directly with Microsoft.Extensions.DependencyInjection. You create static extension classes that wrap IServiceCollection registration calls, then invoke them in Program.cs to compose modular dependency injection blocks.

Split dependency injection registrations into separate extension methods when managing large ASP.NET Core codebases seeking reusable production configurations. This approach is ideal when Program.cs becomes oversized or when multiple test projects need to compose specific feature services independently.