Issues setting up Entity Framework (code first) on an ASP.Net MVC project

Assuming you are using Identity to create tables to store user data,etc. There are a few pieces to the puzzle you'll want here:

A class that inherits from IdentityDbContext (not just DbContext since you want the Identity tables as well):

 public class MyContext: IdentityDbContext<ApplicationUser>
  {
    /// <summary>
    /// default project context
    /// </summary>
    public MyContext() : base("yourConnectionString")
    {
      //optional but I use: Configuration.LazyLoadingEnabled = false;
      //optional but I use: Configuration.ProxyCreationEnabled = false;
    }

    public static MyContext Create()
    {
      return new MyContext();
    }

    protected override void OnModelCreating(DbModelBuilder modelBuilder)
    {
      base.OnModelCreating(modelBuilder);

      //remove cascade deletions; we handle our deletions manually in the code
      //optional but I use: modelBuilder.Conventions.Remove<OneToManyCascadeDeleteConvention>();
      //optional but I use: modelBuilder.Conventions.Remove<ManyToManyCascadeDeleteConvention>();
    }

    //add a dbset for each model class that you want to make a table for
    //you do NOT need to do this for the Identity provided classes
    public DbSet<Movie> Movies { get; set; }
    public DbSet<Customer> Custoemrs { get; set; }
  }

a web.config entry for your connection string (note dependending on your db, the connectionString="..." section of this may be different for you):

<configuration>
  <configSections>
    <connectionStrings>
      <add name="yourConnectionString" connectionString="Data Source=localhost;Initial Catalog=ProEdVerificationPortalDb;Integrated Security=True;" providerName="System.Data.SqlClient" />
    </connectionStrings>
  </configSections>
</configuration>

A class to represent your application users:

public class ApplicationUser : IdentityUser
{
   //only application user fields that are specific to your application
   //i.e: any fields that the default AspNetUsers table does not have
   public DateTime? InactiveDate { get; set; }
}

Depending on how you have migrations set up, this may just generate a migration but not actually run it. You may need to type command update-database into the package manager console after you've added the migration so that the migration is actually run.