.Net core startup base class

Question

Wishing to use .Net core to create a suite of micro services, I was thinking of creating a base class for the Startup class which would be responsible for configuring common features such as logging, authentication, endpoint health checks therefore standardizing all our services.

I was surprised however that such a pattern does not seem to be mentioned. Is the preferred pattern to use custom middleware for common functionality instead? Any thoughts or experience in relation to this dilemma would be appreciated.

Answer 1

Create extensions methods for IServiceCollection and/or IApplicationBuilder interfaces in Microsoft.Extensions.DependencyInjection namespace:

public static IServiceCollection AddAllCoolStuff(this IServiceCollection services)
{
    if (services == null)
    {
        throw new ArgumentNullException(nameof(services));
    }

    services.AddSingleton<FooService>();
    services.AddTransient<IBooService, BooService>();
    ...

    return services;
}

public static IApplicationBuilder UseAllCoolStuff(this IApplicationBuilder app)
{
    if (app == null)
    {
        throw new ArgumentNullException(nameof(app));
    }

    app.UseMiddleware<SomeCoolMiddleware>();
    ...

    return app;
}

And use them in your Startup's:

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddAllCoolStuff();
    }

    public void Configure(IApplicationBuilder app, ILoggerFactory loggerFactory)
    {
        app.UseAllCoolStuff();
    }
}