SDCores 1.0.0

SDCores in .Net core

2. DependencyInjectionConfiguration

Why should use DependencyInjectionConfiguration ?

Usually we need:

public interface IServiceA
{
    void Do();
}

public class ServiceA :IServiceA
{
    void Do(){
        // implementation 
    }
}

public class TestController : ControllerBase
{
    private readonly IServiceA _serviceA;

    public TestController(IServiceA serviceA)
    {
        _serviceA = serviceA;
    }
}

and then in Program.cs

using ...
var builder = WebApplication.CreateBuilder(args);
...
builder.Services.AddScoped<IServiceA, ServiceA>();
...

And if you have forgot to register your service(s) to the DI engine. This can be so annoying sometimes considering that you have already coded your service interface and its implementation and even used it by constructor injection in your controller or another service

System.InvalidOperationException: Unable to resolve service for type ... 
at Microsoft.Extensions.DependencyInjection.ActivatorUtilities.GetService(IServiceProvider sp, ...

That's why you should use DependencyInjectionConfiguration

[DependencyInjectionAttribute(ServiceLifetime.Transient)]
public interface IServiceA
{
    void Do();
}

And then just add this line to your ConfigureService method of your Program.cs like this

builder.Services.AddDependencyInjectionConfiguration(typeof(Program));

In every service interface by using the DependencyInjectionAttribute annotation and passing your desired service lifetime, your service will be automatically registered in the dotnet core DI engine.