I believe the following should work for you
public class Address
{
public int AddressId { get; set; }
public string AddressString { get; set; }
}
public class User
{
public int UserId { get; set; }
public virtual ICollection<Address> Addresses { get; set; }
}
public class House
{
public int HouseId { get; set; }
public virtual Address Address { get; set; }
}
public class TestContext : DbContext
{
public DbSet<Address> Addresses { get; set; }
public DbSet<User> Users { get; set; }
public DbSet<House> Houses { get; set; }
protected override void OnModelCreating(DbModelBuilder modelBuilder)
{
modelBuilder.Entity<User>().HasMany(u => u.Addresses).WithMany();
modelBuilder.Entity<House>().HasRequired(h => h.Address).WithOptional().Map(m => m.MapKey("AddressId"));
}
}
Note that it's often better to specify the foreign key fields yourself, which can make life a lot easier for you later on. If you do this, then you can choose to rewrite House as the following:
public class House
{
public int HouseId { get; set; }
public int AddressId { get; set; }
public virtual Address Address { get; set; }
}
Convention will link up AddressId and Address. If you have a one-to-one mapping between House and Address, you could also link them on their primary keys:
public class House
{
[ForeignKey("Address")]
public int HouseId { get; set; }
public virtual Address Address { get; set; }
}
You mentioned that you would like to enforce at least one address - this isn't possible with a one-to-many relationship. You could only do this if a user had exactly one address, at which point you could add a required AddressId property on the User class.
One other comment - you made everything virtual in your code. You only need to make navigation properties virtual.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…