Database initialization strategy Code First

Question

I have an ASP.NET-MVC application with Migration enabled and SimpleMemberShipProvider configured to use my database with some extra tables/fields.

My question is, where to put my database initialization? Because i'm still developing it, i'm okay with dropping the database/tables and data and recreate it.

I have put it in the configuration.cs file, but i'm not sure if that's the place for the database initializer.

namespace CFContext.Migrations
{
    using System;
    using System.Data.Entity;
    using System.Data.Entity.Migrations;
    using System.Linq;
    using WebMatrix.WebData;
    using System.Web.Security;
    using System.Collections.Generic;

internal sealed class Configuration : DbMigrationsConfiguration<DataContext>
{
    public Configuration()
    {
        Database.SetInitializer(new DropCreateDatabaseAlways<DataContext>());
        //Database.SetInitializer(new DropCreateDatabaseIfModelChanges<DataContext>());
        AutomaticMigrationsEnabled = true;
        AutomaticMigrationDataLossAllowed = true;
    }

    protected override void Seed(DataContext context)
    {
        //  This method will be called after migrating to the latest version.

        //  You can use the DbSet<T>.AddOrUpdate() helper extension method 
        //  to avoid creating duplicate seed data. E.g.
        //
        //    context.People.AddOrUpdate(
        //      p => p.FullName,
        //      new Person { FullName = "Andrew Peters" },
        //      new Person { FullName = "Brice Lambson" },
        //      new Person { FullName = "Rowan Miller" }
        //    );
        //

        SeedMembership(context);
    }

    private void SeedMembership(DataContext context)
    {
        WebSecurity.InitializeDatabaseConnection("DefaultConnection", "UserProfile", "UserId", "UserName", autoCreateTables: true);

        var roles = (SimpleRoleProvider)Roles.Provider;
        var membership = (SimpleMembershipProvider)System.Web.Security.Membership.Provider;

        if (!roles.RoleExists("Administrator"))
            roles.CreateRole("Administrator");

        if (membership.GetUser("Username0", false) == null)
        {

        }
      }
    }
}

Answer 1

public class ContextInitializer : CreateDatabaseIfNotExists<Context>
{     
    private static void InitializeWebSecurity()
    {
        if (WebSecurity.Initialized)
            return;

        WebSecurity.InitializeDatabaseConnection(
            connectionStringName: "DefaultConnection",
            userTableName: "User",
            userIdColumn: "Id",
            userNameColumn: "Email",
            autoCreateTables: true);

        Roles.CreateRole("Admin");
        Roles.CreateRole("Customer");
    }       

    protected override void Seed(Context context)
    {
        InitializeWebSecurity();

        // more seeding
        context.SaveChanges();
    }
}

public class MvcApplication : System.Web.HttpApplication
{
    protected void Application_Start()
    {
        AreaRegistration.RegisterAllAreas();
        WebApiConfig.Register(GlobalConfiguration.Configuration);
        FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
        RouteConfig.RegisterRoutes(RouteTable.Routes);
        BundleConfig.RegisterBundles(BundleTable.Bundles);
        AuthConfig.RegisterAuth();
        DatabaseConfig.RegisterDatabase();
        AutoMapperConfig.RegisterConfig();

        // Set the initializer here
        Database.SetInitializer(new ContextInitializer());

        // Now initialize it
        using (var context = new Context())
        {
            context.Database.Initialize(false);
        }

        // Double check seeding has initalized, if not
        // We initialize it here to make sure.
        if (!WebSecurity.Initialized)
        {
            WebSecurity.InitializeDatabaseConnection(
                connectionStringName: "DefaultConnection", 
                userTableName: "User", 
                userIdColumn: "Id", 
                userNameColumn: "Email", 
                autoCreateTables: false);
        }
    }
}

You should be able to create migrations the same way with this setup.