Ladislav was right to propose the problem of inheritance. It seems that Entity Framework 4.3 and Entity Framework 5 behave a little differently when it comes to code scenarios “Table configuration to hierarchy”.
In this case, I had four derived types, each of which had its own configuration class derived from EntityTypeConfiguration<T> . The underlying abstract type did not have a configuration registered in the model builder. This is not a problem in EF 4.3, which simply created a table named after the base type with the Discriminator column to distinguish between the types.
To get the same behavior with EF 5, you had to create an empty configuration class
public class MyBaseConfiguration : EntityTypeConfiguration<MyBase> {
and then register it using the model builder
public class MyContext : DbContext { protected override void OnModelCreating(DbModelBuilder modelBuilder) { modelBuilder.Configurations.Add(new MyBaseConfiguration());
source share