Using Asp.Net Identity with custom database [duplicate]

Question

I copied default AspNet Identity tables (AspNetUsers, AspNetLogin etc) into my database and everything worked fine. Then I changed their names and made my own context with the following method:

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

        modelBuilder.Entity<IdentityUser>()
            .ToTable("tblUsers", "dbo");

        modelBuilder.Entity<IdentityRole>()
            .ToTable("tblRoles", "dbo");

        modelBuilder.Entity<IdentityUserRole>()
            .ToTable("tblUserRoles", "dbo");

        modelBuilder.Entity<IdentityUserClaim>()
            .ToTable("tblUserClaims", "dbo");

        modelBuilder.Entity<IdentityUserLogin>()
            .ToTable("tblUserLogins", "dbo");
    }

But it seems like the application is still looking for tables with old names as I'm getting error:

Please, tip me what are the neccessary changes that I haven't done ?

did you used the migration to update the database?

Cristian Szpisjak
– Cristian Szpisjak

2016-10-25 16:11:43 +00:00
Commented Oct 25, 2016 at 16:11 — Cristian Szpisjak
– Cristian Szpisjak, Commented Oct 25, 2016 at 16:11

Community · Accepted Answer · 2017-05-23 12:06:43Z

According to How can I change the table names when using Visual Studio 2013 ASP.NET Identity? this should work:

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

    modelBuilder.Entity<IdentityUser>().ToTable("MyUsers").Property(p => p.Id).HasColumnName("UserId");
    modelBuilder.Entity<ApplicationUser>().ToTable("MyUsers").Property(p => p.Id).HasColumnName("UserId");
    modelBuilder.Entity<IdentityUserRole>().ToTable("MyUserRoles");
    modelBuilder.Entity<IdentityUserLogin>().ToTable("MyUserLogins");
    modelBuilder.Entity<IdentityUserClaim>().ToTable("MyUserClaims");
    modelBuilder.Entity<IdentityRole>().ToTable("MyRoles");
}

also make sure you're not falling into a trap that ASP.NET Identity uses its default aspnetdb.mdf database and check your web.config for something like this:

<connectionStrings>
   <remove name="LocalSqlServer" />
   <add connectionString="yourdatabase" name="LocalSqlServer" providerName="System.Data.SqlClient" />
</connectionStrings>

Collectives™ on Stack Overflow

Using Asp.Net Identity with custom database [duplicate]

1 Answer 1

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Linked

Related