Run database migrations using Entity Framework ASP.NET Core on application start

Question

I would like to automatically run a database migration on application start in ASP.NET Core 2.0 and EntityFramework Core 2.0.

I have found Run database migrations using Entity Framework core on application start. However, my connection strings are stored in the environment variables so they would not be found until the .AddEnvironmentVariables() are called in the Configure method.

How to call the db.Database.Migrate() or how to properly do the database migration (in Azure Web App) via Continuous Deployment and staging environments?

public class Startup
{
    private IConfigurationRoot Configuration { get; set; }

    public void ConfigureServices(IServiceCollection services)
    {
        services.AddMvc();

        services.AddDbContext<ClientContext>(options => options.UseSqlServer(this.Configuration.GetConnectionString("AppService")));
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app.UseMvc();

        this.Configuration = new ConfigurationBuilder()
            .SetBasePath(env.ContentRootPath)
            .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
            .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
            .AddEnvironmentVariables()
            .Build();
    }

    // public void Configure(IApplicationBuilder app, ClientContext db)
    // {
    //     db.Database.Migrate();
    // }
}

Why not just call db.Database.Migrate() at the end of the Configure() method? After connection strings are set. — Stephen Wilson
– Stephen Wilson, Commented Jul 19, 2017 at 13:19
If I add the ClientContext db parameter to the Configure method, the ClientContext will get instantiated before the Configure call is made. The ClientContext gets the options as a constructor parameter which tries to retrieve the AppService connection string before the Configuration object is configured (or event instantiated). Or is my understanding wrong? — alik
– alik, Commented Jul 19, 2017 at 13:22

Stephen Wilson · Accepted Answer · 2017-07-19 13:34:49Z

4

Based on you comment above I would try this:

public void Configure(IApplicationBuilder app, IServiceProvider serviceProvider)
{
    app.UseMvc();

    this.Configuration = new ConfigurationBuilder()
        .SetBasePath(env.ContentRootPath)
        .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
        .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
        .AddEnvironmentVariables()
        .Build();

    var db = serviceProvider.GetService<ClientContext>();
    db.Database.Migrate();
}

This is manually resolving the ClientContext after the Environment variables have been set up and therefore it won't fail the parameter injection.

EDIT: The error you're getting can be resolved by following the steps in this SO question

edited Jul 19, 2017 at 13:34

answered Jul 19, 2017 at 13:25

Stephen Wilson

1,5141 gold badge15 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

alik Over a year ago

I guess that the ClientContext life time is managed by the runtime so there is no need to add "using" statement, right?

alik Over a year ago

I am getting Cannot resolve scoped service 'AppService.ClientContext' from root provider..

Stephen Wilson Over a year ago

See my edit above, no point me re-writing out those steps as well :-)

alik Over a year ago

The only thing I am not very happy of is that the app needs to work under a full sql admin to make this work. But that is another issue.

Collectives™ on Stack Overflow

Run database migrations using Entity Framework ASP.NET Core on application start

1 Answer 1

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related