Entity Framework Code First - Advantages and disadvantages of Fluent Api vs Data Annotations

ef-fluent-api entity-framework

Question

When creating a database using Entity Framework code-first, a lot of the database model is can be extracted from the code. Fluent API and/or Attributes can be used to fine tune the model.

What are the advantages and disadvantages of Fluent Api in comparison to Data Annotations? In other words: Even if in certain situations both methods can be used, in what cases should one method prevail above the other?

1
114
9/25/2018 8:54:34 AM

Accepted Answer

Everything what you can configure with DataAnnotations is also possible with the Fluent API. The reverse is not true. So, from the viewpoint of configuration options and flexibility the Fluent API is "better".

Configuration examples (for sure not a full list) which are possible in the Fluent API but not with DataAnnotations (as far as I can see):

  • Switch off cascading deletes:

    .WillCascadeOnDelete(false)

  • Specify foreign key column name in the database when the key isn't exposed in your object model:

    .Map(conf => conf.MapKey("MyForeignKeyID"))

  • Fine granular tuning of relationships, especially in all cases where only one side of an association is exposed in the object model:

    .WithMany(...), WithOptional(...), WithRequiredDependent(...), WithRequiredPrincipal(...)

  • Specification of inheritance mapping between object model and database tables (Table-Per-Hierarchy, Table-Per-Type, Table-Per-Concrete-Class):

    .Map<TDerived>(Action<EntityMappingConfiguration<TDerived>> ...)

Edit: Microsoft considers the Fluent API as an "advanced feature" (Quote from here):

The fluent API is considered a more advanced feature and we would recommend using Data Annotations unless your requirements require you to use the fluent API.

But in my opinion you reach the limitations of DataAnnotations very quickly (except perhaps for extremely simple object models). If you cannot fine tune your model with DataAnnotations anymore your last resort is to follow the default mapping conventions (by naming your properties according to those rules). Currently you cannot overwrite the conventions (only disable them; MS announced to give configuration options for the conventions in future EF releases). But if you don't want to be forced by the mapping conventions when you define your object model, your only option then is the Fluent API.

Learning the Fluent API is almost a Must imho, the DataAnnotations are a nice-to-have for simple applications.

137
3/18/2011 6:40:33 PM


Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow