当前，我正在使用AspNetCore和以下配置dbcontext：
public class AppDbContext : IdentityDbContext<ApplicationUser, ApplicationRole, string, ApplicationUserClaim, ApplicationUserRole, IdentityUserLogin<string>, ApplicationRoleClaim, IdentityUserToken<string>>
{
public AppDbContext(DbContextOptions<AppDbContext> options)
: base(options)
{ }
所以我想自定义AspNetIdentity，但是为了简单起见，我只在表之间配置了外键：
<string> <string> <string> public class ApplicationUser : IdentityUser
{
public virtual ICollection<ApplicationUserRole> UserRoles { get; set; }
public virtual ICollection<ApplicationUserClaim> UserClaims { get; set; }
}
public class ApplicationRole : IdentityRole
{
public virtual ICollection<ApplicationUserRole> UserRoles { get; set; }
public virtual ICollection<ApplicationRoleClaim> RoleClaims { get; set; }
}
public class ApplicationRoleClaim : IdentityRoleClaim<string>
{
public virtual ApplicationRole Role { get; set; }
}
public class ApplicationUserRole : IdentityUserRole<string>
{
public int Id { get; set; }
public virtual ApplicationRole Role { get; set; }
public virtual ApplicationUser User { get; set; }
}
public class ApplicationUserClaim : IdentityUserClaim<string>
{
public virtual ApplicationUser User { get; set; }
}
以下是派生类为特定的自定义身份模型实现IEntityTypeConfiguration。
public class ApplicationUserEntityBuilder : IEntityTypeConfiguration<ApplicationUser>
{
public void Configure(EntityTypeBuilder<ApplicationUser> builder)
{
// still use default table name
builder.ToTable("AspNetUsers");
builder.Property(p => p.Id)
.HasColumnType("CHAR(36)");
}
}
public class ApplicationRoleEntityBuilder : IEntityTypeConfiguration<ApplicationRole>
{
public void Configure(EntityTypeBuilder<ApplicationRole> builder)
{
// still use default table name
builder.ToTable("AspNetRoles");
}
}
public class ApplicationUserClaimEntityBuilder : IEntityTypeConfiguration<ApplicationUserClaim>
{
public void Configure(EntityTypeBuilder<ApplicationUserClaim> builder)
{
builder.Property(p => p.UserId)
.HasColumnName(nameof(ApplicationUserClaim.UserId))
.HasColumnType("CHAR(36)");
builder.HasOne(p => p.User)
.WithMany(u => u.UserClaims)
.HasForeignKey(p => p.UserId)
.IsRequired();
}
}
public class ApplicationUserRoleEntityBuilder : IEntityTypeConfiguration<ApplicationUserRole>
{
public void Configure(EntityTypeBuilder<ApplicationUserRole> builder)
{
// still use default table name
builder.ToTable("AspNetUserRoles");
builder.HasKey(p => p.Id);
builder.Property(p => p.Id)
.ValueGeneratedOnAdd();
builder.HasOne(p => p.Role)
.WithMany(r => r.UserRoles)
.HasForeignKey(p => p.RoleId)
.IsRequired();
builder.HasOne(p => p.User)
.WithMany(r => r.UserRoles)
.HasForeignKey(p => p.UserId)
.IsRequired();
}
}
public class ApplicationRoleClaimEntityBuilder : IEntityTypeConfiguration<ApplicationRoleClaim>
{
public void Configure(EntityTypeBuilder<ApplicationRoleClaim> builder)
{
// still use default table name
builder.ToTable("AspNetRoleClaims");
builder.HasKey(p => p.Id);
builder.Property(p => p.Id)
.ValueGeneratedOnAdd();
builder.Property(p => p.RoleId)
.HasColumnName(nameof(ApplicationRoleClaim.RoleId))
.HasColumnType("CHAR(36)");
builder.HasOne(p => p.Role)
.WithMany(r => r.RoleClaims)
.HasForeignKey(p => p.RoleId)
.IsRequired();
}
}
所有这些流利的API配置完成之后，EF Core在表AspNetRoleClaims，AspNetUserClaims，AspNetUserRoles中生成了重复的外键
migrationBuilder.CreateTable(
name: "AspNetRoleClaims",
columns: table => new
{
Id = table.Column<int>(nullable: false)
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
RoleId = table.Column<string>(type: "CHAR(36)", nullable: false),
ClaimType = table.Column<string>(nullable: true),
ClaimValue = table.Column<string>(nullable: true),
RoleId1 = table.Column<string>(nullable: true) // DUPLICATE
},
constraints: table =>
{
table.PrimaryKey("PK_AspNetRoleClaims", x => x.Id);
table.ForeignKey(
name: "FK_AspNetRoleClaims_AspNetRoles_RoleId",
column: x => x.RoleId,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetRoleClaims_AspNetRoles_RoleId1",
column: x => x.RoleId1,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
});
migrationBuilder.CreateTable(
name: "AspNetUserClaims",
columns: table => new
{
Id = table.Column<int>(nullable: false)
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
UserId = table.Column<string>(type: "CHAR(36)", nullable: false),
ClaimType = table.Column<string>(nullable: true),
ClaimValue = table.Column<string>(nullable: true),
UserId1 = table.Column<string>(nullable: true) //DUPLICATE
},
constraints: table =>
{
table.PrimaryKey("PK_AspNetUserClaims", x => x.Id);
table.ForeignKey(
name: "FK_AspNetUserClaims_AspNetUsers_UserId",
column: x => x.UserId,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetUserClaims_AspNetUsers_UserId1",
column: x => x.UserId1,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
});
migrationBuilder.CreateTable(
name: "AspNetUserRoles",
columns: table => new
{
UserId = table.Column<string>(nullable: false),
RoleId = table.Column<string>(nullable: false),
Id = table.Column<int>(nullable: false)
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn),
RoleId1 = table.Column<string>(nullable: true), //DUPLICATE
UserId1 = table.Column<string>(nullable: true) //DUPLICATE
},
constraints: table =>
{
table.PrimaryKey("PK_AspNetUserRoles", x => new { x.UserId, x.RoleId });
table.UniqueConstraint("AK_AspNetUserRoles_Id", x => x.Id);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetRoles_RoleId",
column: x => x.RoleId,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetRoles_RoleId1",
column: x => x.RoleId1,
principalTable: "AspNetRoles",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetUsers_UserId",
column: x => x.UserId,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Cascade);
table.ForeignKey(
name: "FK_AspNetUserRoles_AspNetUsers_UserId1",
column: x => x.UserId1,
principalTable: "AspNetUsers",
principalColumn: "Id",
onDelete: ReferentialAction.Restrict);
});
如果我做错了任何事情，请帮我复习。谢谢大家。
更新1
因为导航属性导致重复的外键。如果在自定义身份模型中删除这些属性，则EFCore将不会生成“ DuplicateProperty1”。那我现在要做什么？
最终更新
根本原因是我将base.OnModelCreating(builder);放在方法protected override void OnModelCreating(ModelBuilder builder)的末尾。因此，我配置了内部派生类的所有东西都实现了IEntityTypeConfiguration，它将被基类覆盖。最终版本如下：
public class AppDbContext : IdentityDbContext<ApplicationUser, ApplicationRole, string, ApplicationUserClaim, ApplicationUserRole, IdentityUserLogin<string>, ApplicationRoleClaim, IdentityUserToken<string>>
{
public AppDbContext(DbContextOptions<AppDbContext> options)
: base(options)
{ }
protected override void OnModelCreating(ModelBuilder builder)
{
base.OnModelCreating(builder);
var entitiesBuilder = Assembly.GetExecutingAssembly()
.GetTypes()
.Where(type => type.ContainsGenericParameters == false && type.GetInterface(nameof(IEntityBuilder)) != null)
.ToList();
foreach (var entityBuilder in entitiesBuilder)
{
var instance = Activator.CreateInstance(entityBuilder) as IEntityBuilder;
instance.RunConfiguration(builder);
}
// base.OnModelCreating(builder); move this line to the beginning of this method
}
}
答案 0 :(得分：1)
表之间的关系已经在 Identity的 IdentityDbContext default configuration中设置。这意味着您不必显式地指定它们（使用导航性道具/流畅的api配置）。
但是，您似乎希望使用Guid / Uuid而不是string作为主键/外键的列类型。如果是这样，实现此目标的正确方法是使用已经继承的类的通用变体。
例如，您可以仅定义需要扩展的类并为其添加其他属性-这些将包括在数据库迁移中：
public class ApplicationUser : IdentityUser<Guid>
{
}
public class ApplicationRole : IdentityRole<Guid>
{
}
除此之外，您的DbContext必须继承IdentityDbContext的适当变体：
public class ApplicationUserDbContext : IdentityDbContext<ApplicationUser, ApplicationRole, Guid>
{
}
之后，您的迁移将生成一个脚本，以将PK / FK更改为正确的列类型。如果您需要从 Identity 扩展其他类型，则可以使用IdentityDbContext的大多数通用变体，它需要一堆type parameters。
答案 1 :(得分：0)
之所以发生这种情况，是因为当您从身份模型继承时，它已经具有此关系和其他指定的属性。您的代码只是在实体之间添加了其他关系。您可以在文档中了解有关身份定制的更多信息：https://docs.microsoft.com/en-us/aspnet/core/security/authentication/customize-identity-model?view=aspnetcore-2.1
答案 2 :(得分：0)
确保像下面的IEntityTypeConfiguration中那样配置AppDbContext。
public class ApplicationDbContext : IdentityDbContext<ApplicationUser, ApplicationRole, string, ApplicationUserClaim, ApplicationUserRole, IdentityUserLogin<string>, ApplicationRoleClaim, IdentityUserToken<string>>
{
public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
: base(options)
{ }
protected override void OnModelCreating(ModelBuilder builder)
{
base.OnModelCreating(builder);
builder.ApplyConfiguration(new ApplicationUserEntityBuilder());
builder.ApplyConfiguration(new ApplicationRoleEntityBuilder());
builder.ApplyConfiguration(new ApplicationUserClaimEntityBuilder());
builder.ApplyConfiguration(new ApplicationUserRoleEntityBuilder());
builder.ApplyConfiguration(new ApplicationRoleClaimEntityBuilder());
}
}