auto-di-registration

Automate dependency injection service registration by scanning assemblies to dynamically map service implementations to their interfaces. Simply input the assembly name, such as 'Template.BusinessLogic', to eliminate manual configuration for each service.

Strategy management during assembly scanning handles multiple implementations of the same interface by registering them as a strategy family. This allows your dependency injection container to resolve the correct implementation dynamically based on runtime requirements.

Yes, you can exclude specific components like DbContext and Identity from automatic DI registration. The tool provides manual wiring exemptions to ensure components requiring special configuration bypass the automated assembly scanning process.

The best way to map service implementations without manual errors is using automated assembly scanning. This dynamically discovers and registers services implementing specific interfaces, reducing inconsistencies in your dependency injection container setup.

Dependency injection setup fails with multiple implementations if they are not registered as a strategy family. Without strategy management, the DI container cannot distinguish between multiple service implementations mapped to the same interface.

No, you do not need to manually configure each service. By scanning assemblies and automatically mapping implementations to interfaces, the tool streamlines the dependency injection configuration process by simply including the correct assembly.