Updating Multiple MVC 5 Databases

Question

I have two contexts working with visual studio 2013. One for IdentityModel and the other context that I created for the main database. The problem I encountered is when I run the update database in the package manager console, it creates the ApplicationDBContext database in both cases. One that is never created for my main database because it seems like it sees it as ApplicationDBContext. I tried Enable-Migrations -ContextTypeName DI_MVC.Models.DIDBContext and does not create the main database tables for the DIDBContext class. I was able to do this in visual studio 2012 without problems when creating the database. However, this was without ApplicationDBContext. Any help on what I am doing wrong will be greatly appreciated.

Below are my 2 code files. Normal IdentityModel and my DIDBContext class that I created. I will also show the web.config file along with the database connections. 2.mdf files are created in the App_Data folder, but both databases contain membership tables.

using System;
using System.Data.Entity;
using System.ComponentModel.DataAnnotations.Schema;
using System.Data.Entity.ModelConfiguration.Conventions;

namespace DI_MVC.Models
{
    public class DIDBContext : DbContext
    {
        public DIDBContext()
            : base("DIDBContext")
        {

        }

        public DbSet<DI_ConnectionStrings_CSI> CSIs { get; set; }
        public DbSet<DI_DropDownValues_DDV> DDVs { get; set; }
        public DbSet<DI_Types_DIT> DITs { get; set; }
        public DbSet<DI_FORM_DIF> DIFs { get; set; }
        public DbSet<DI_FormTabs_DFT> DFTs { get; set; }
        public DbSet<DFI_FormSections_DFS> DFSs { get; set; }
        public DbSet<DI_FormElements_DFE> DFEs { get; set; }
        public DbSet<DI_DFE_DFS_DDD> DDDs { get; set; }

        protected override void OnModelCreating(DbModelBuilder modelBuilder)
        {
            modelBuilder.Entity<DI_DFE_DFS_DDD>().HasKey(k => new { k.DDD_DFS_ID, k.DDD_DFE_ID });
            modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();
        }
    }
}


using Microsoft.AspNet.Identity.EntityFramework;
using System;
using System.Data.Entity;
using System.ComponentModel.DataAnnotations.Schema;
using System.Data.Entity.ModelConfiguration.Conventions;

namespace DI_MVC.Models
{
    // You can add profile data for the user by adding more properties to your ApplicationUser class, please visit http://go.microsoft.com/fwlink/?LinkID=317594 to learn more.
    public class ApplicationUser : IdentityUser
    {
        public DateTime BirthDate { get; set; }
        public string FirstName { get; set; }
        public string LastName { get; set; }
    }

    public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
    {
        public ApplicationDbContext()
            : base("DefaultConnection")
        {

        }
    }

}

<connectionStrings>
    <add name="DefaultConnection" connectionString="Data Source=(LocalDb)\v11.0;AttachDbFilename=|DataDirectory|\aspnet-DI_MVC-meohmeohmy.mdf;Initial Catalog=aspnet-DI_MVC-meohmeohmy;Integrated Security=True"
      providerName="System.Data.SqlClient" />
    <add name="DIDBContext" connectionString="Data Source=(LocalDb)\v11.0;AttachDbFilename=|DataDirectory|\aspnet-DI_MVC-MainDB.mdf;Initial Catalog=aspnet-DI_MVC-MainDB;Integrated Security=True"
      providerName="System.Data.SqlClient" />
  </connectionStrings>

Answer 1

You are not alone. It would be wise that if you enabled migration for one DbContext, it would only update the DbContext so that the migration is enabled, or at least let you specify which DbContext you want to update. However, it is not.

Consider - this and this .

TL; DR Enable-Migrations -EnableAutomaticMigrations