Is Dependency Injection auto registration bad practice?

Programming
, ,
1

Using Dependency Injection with .NET Core

When working with .NET Core, the default dependency injection container is Microsoft.Extensions.DependencyInjection.

Previously, when using Unity as an IOC container, classes could be auto registered using convention over configuration.

However, Microsoft.Extensions.DependencyInjection does not have this feature as an option.

Before replacing this option with a 3rd party IOC solution, is there a reason why the standard Dependency Injection framework does not have autoregistration as a feature? Is autoregistration now considered bad practice? If so, why is it better to specify everything explicitly?

public void ConfigureServices(IServiceCollection services)
{
    services.AddControllers();
    services.AddSingleton<IMyService, MyService>();
}
2

Autoregistration is not a feature of Microsoft.Extensions.DependencyInjection because it goes against the principle of explicit dependencies, which is considered a best practice. By explicitly registering dependencies, the code is easier to understand, maintain, and test. Therefore, it is recommended to specify all dependencies explicitly.