How you can use keyed providers in ASP.NET Core

var builder = WebApplication.CreateBuilder(args);
// Register a number of keyed providers for the ICustomLogger interface
builder.Companies.AddKeyedScoped("file");
builder.Companies.AddKeyedScoped("database");
builder.Companies.AddKeyedScoped("occasion");
var app = builder.Construct();

Be aware how the FileLogger, DatabaseLogger, and EventLogger providers are registered utilizing the keys "file", "database", and "occasion", respectively.

Inject the keyed logger providers

We will use the [FromKeyedServices] attribute to inject a particular implementation of our logger service in our minimal API endpoints as proven within the code snippet given under.

app.MapGet("/customlogger/file", ([FromKeyedServices("file")] ICustomLogger fileLogger) =>
{
    fileLogger.Log("This textual content is written to the file system.");
    return Outcomes.Okay("File logger executed efficiently.");
});
app.MapGet("/customlogger/db", ([FromKeyedServices("database")] ICustomLogger databaseLogger) =>
{
    databaseLogger.Log("This textual content is saved within the database.");
    return Outcomes.Okay("Database logger executed efficiently.");
});
app.MapGet("/customlogger/occasion", ([FromKeyedServices("event")] ICustomLogger logger) =>
{
    logger.Log("This textual content is recorded within the occasion system.");
    return Outcomes.Okay("Occasion logger executed efficiently.");
});

Thus, by utilizing DI and keyed providers, we will implement every of our logger providers as soon as, then merely ask for the fitting sort of the logger once we want one with out having to make use of a manufacturing unit to instantate the logger. And at any time when we need to swap the implementations—from FileLogger to DatabaseLogger, for instance—all we have to do is change the configuration we specied whereas registering the providers with the container. The DI system will plug in the fitting logger robotically at run time.