Entity Framework Code First – Advantages and disadvantages of Fluent Api vs Data Annotations [closed]

by

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.

More Related Contents:

  1. ORM Entities vs. Domain Entities under Entity Framework 6.0
  2. How do I detach objects in Entity Framework Code First?
  3. No executable found matching command “dotnet-ef”
  4. Setting unique Constraint with fluent API?
  5. Entity Framework Code First – No Detach() method on DbContext
  6. Entity Framework validation with partial updates
  7. Solution for “Validation failed for one or more entities. See ‘EntityValidationErrors’ property for more details.”
  8. NOT using repository pattern, use the ORM as is (EF)
  9. How do you update an edmx file with database changes?
  10. Cascading deletes with Entity Framework – Related entities deleted by EF
  11. EF Query With Conditional Include
  12. Entity Framework CTP 4 – Code First Custom Database Initializer
  13. How do I singularize my tables in EF Code First?
  14. Set decimal(16, 3) for a column in Code First Approach in EF4.3 [duplicate]
  15. How to create index in Entity Framework 6.2 with code first
  16. DbSet.Find method ridiculously slow compared to .SingleOrDefault on ID
  17. Efficient way to do bulk insert/update with Entity Framework
  18. Entity Framework and calling context.dispose()
  19. Stuffing an anonymous type in ViewBag causing model binder issues
  20. EntityFramework Core automatic migrations
  21. What is the syntax for self referencing foreign keys in EF Code First?
  22. Entity Framework 4.1+ many-to-many relationships change tracking
  23. Include Grandchildren in EF Query
  24. check constraint entity framework
  25. int to string in Entity Framework
  26. Paging in Entity Framework
  27. Using SimpleMembership with EF model-first
  28. Entity Framework: Inheritance and Include
  29. Entity Framework – Get List of Tables
  30. Entity framework code first delete with cascade

Leave a Comment