Aspnet identity tables reappear

i an using aspnet identity in one of my project my project entities are in different project where as identy is a seperate project(all knows)

i want to link some tables with identity i have linked thm successfully data is also entering appropriately in every table(identity + my project tables)

public class ApplicationDbContext : IdentityDbContext
{
public ApplicationDbContext()
: base("DefaultConnection", throwIfV1Schema: false)
{
Database.SetInitializer(new MigrateDatabaseToLatestVersion());
// Database.SetInitializer(new DropCreateDatabaseIfModelChanges());
//Database.SetInitializer(new DropCreateDatabaseAlways());
//Database.SetInitializer(new SchoolDBInitializer());

}

automaticmigrations are set to true in configuration.cs of migartion folder of this project

i have changed my identity db table names using this
protected override void OnModelCreating(DbModelBuilder modelBuilder)
{
base.OnModelCreating(modelBuilder);

modelBuilder.Entity().ToTable("Users");
modelBuilder.Entity().ToTable("Role");
modelBuilder.Entity().ToTable("UserRole");
modelBuilder.Entity().ToTable("Claim");
modelBuilder.Entity().ToTable("Login");

}

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

}

public virtual Employer Employer { get; set; }
public virtual Candidate Candidate { get; set; }

above lines link my tables to aspnet identity

on registration i entered data in one of my tables data entered successfully in identity and my tables but all identity tables regenerate with their original names with no data and other tables have data what i inserted.this problem is little annoying.if i manually delete these tables and next time register any employer these tables will regenerate again.

how to handle this.

t looks like you are experiencing issues with Identity tables regenerating with their original names and no data. The problem might be related to the migrations and database initialization strategies you are using.

Here are a few steps you can take to handle this issue:

Check Migration History: Ensure that your migrations are being applied correctly. You can check the migration history table in your database. Look at the __MigrationsHistory table and make sure that the latest migration has been applied.
Remove Existing Migrations: If you are still facing issues, you can try removing all existing migrations and then recreating them. Delete all migration files in your Migrations folder, except for the Configuration.cs file. After that, you can run the following commands in the Package Manager Console:
```
Update-Database -TargetMigration:0 Add-Migration InitialCreate Update-Database
```
Seed Data in Configuration.cs: Ensure that you are seeding data in the Configuration.cs file. This file is used for seeding data when the database is created or updated. In your Configuration.cs, you can override the Seed method to add initial data:
```
protected override void Seed(ApplicationDbContext context) { // Add your seeding logic here base.Seed(context); }
```
Database Initialization Strategy: You are using the MigrateDatabaseToLatestVersion initializer, which should apply pending migrations on application startup. Make sure that this initialization strategy is working as expected. Alternatively, you can use other strategies like DropCreateDatabaseIfModelChanges or CreateDatabaseIfNotExists based on your requirements.

Example:
```
Database.SetInitializer(new MigrateDatabaseToLatestVersion());
```
Debugging Migrations: You can use the Update-Database -Verbose command in the Package Manager Console to get more detailed information about what migrations are being applied and if there are any errors.

By following these steps, you should be able to troubleshoot and resolve the issue of Identity tables regenerating with their original names and no data. Remember to backup your database before making significant changes to avoid data loss.

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Jithu Thomas2y ago
t looks like you are experiencing issues with Identity tables regenerating with their original names and no data. The problem might be related to the migrations and database initialization strategies you are using.

Here are a few steps you can take to handle this issue:
1. Check Migration History: Ensure that your migrations are being applied correctly. You can check the migration history table in your database. Look at the __MigrationsHistory table and make sure that the latest migration has been applied.
2. Remove Existing Migrations: If you are still facing issues, you can try removing all existing migrations and then recreating them. Delete all migration files in your Migrations folder, except for the Configuration.cs file. After that, you can run the following commands in the Package Manager Console:
  
  Update-Database -TargetMigration:0 Add-Migration InitialCreate Update-Database
3. Seed Data in Configuration.cs: Ensure that you are seeding data in the Configuration.cs file. This file is used for seeding data when the database is created or updated. In your Configuration.cs, you can override the Seed method to add initial data:
  
  protected override void Seed(ApplicationDbContext context) { // Add your seeding logic here base.Seed(context); }
4. Database Initialization Strategy: You are using the MigrateDatabaseToLatestVersion initializer, which should apply pending migrations on application startup. Make sure that this initialization strategy is working as expected. Alternatively, you can use other strategies like DropCreateDatabaseIfModelChanges or CreateDatabaseIfNotExists based on your requirements.
  
  Example:
  
  Database.SetInitializer(new MigrateDatabaseToLatestVersion());
5. Debugging Migrations: You can use the Update-Database -Verbose command in the Package Manager Console to get more detailed information about what migrations are being applied and if there are any errors.
By following these steps, you should be able to troubleshoot and resolve the issue of Identity tables regenerating with their original names and no data. Remember to backup your database before making significant changes to avoid data loss.