This is compatible with all of the existing DbModelBuilder extension methods since it's just adding a fluent layer on top, but that it does come with some syntactical overhead. Not exactly what you asked for, but doesn't involve mucking around with the supporting code. Haven't fully tested this yet, but it should work if you're comfortable with the syntax:
// First option - like this better because it has less cruft than multiple Has invocations
var modelBuilder = new DbModelBuilder();
var modelConfiguration = new ModelConfigurator(modelBuilder);
modelConfiguration.Entity<Product>().Has(e => {
e.Property(en => en.Name).IsRequired();
e.Property(en => en.UPC).IsRequired();
e.Property(en => en.Price).IsRequired();
e.Property(en => en.Description).IsRequired();}
);
OR
var modelBuilder = new DbModelBuilder();
var modelConfiguration = new ModelConfigurator(modelBuilder);
modelConfiguration.Entity<Product>().Has(e => e.Property(en => en.Name).IsRequired())
.Has(e => e.Property(en => en.UPC).IsRequired())
.Has(e => e.Property(en => en.Price).IsRequired())
.Has(e => e.Property(en => en.Description).IsRequired());
// continue configuring properties, and creating methods on ModelConfigurator as needed
Supporting code:
public class Product{
public string Name {get;set;}
public double Price {get;set;}
public string UPC {get;set;}
public string Description {get;set;}
}
public class ModelConfigurator{
public DbModelBuilder ModelBuilder{get;set;}
public ModelConfigurator(DbModelBuilder modelBuilder){
ModelBuilder = modelBuilder;
}
public EntityConfigurator<TEntity> Entity<TEntity>() where TEntity : class {
var entity = ModelBuilder.Entity<TEntity>();
return new EntityConfigurator<TEntity>(entity);
}
}
public class EntityConfigurator<TEntity> where TEntity : class{
public EntityTypeConfiguration<TEntity> EntityTypeConfiguration {get;set;}
public EntityConfigurator(EntityTypeConfiguration<TEntity> entityTypeConfiguration){
EntityTypeConfiguration = entityTypeConfiguration;
}
public EntityConfigurator<TEntity> Has(Action<EntityTypeConfiguration<TEntity>> a){
a(this.EntityTypeConfiguration);
return this;
}
}
.Property
is used twice for one entity msdn.microsoft.com/en-gb/data/jj591617 – Santororesharper templates
come to mind – Peatroy