How is Entity Framework 4 POCO support compared to NHibernate?

Just wondering if anyone has experience using Entity Framework 4 POCO support and how it stands up compared to NHibernate. If they are the same, I'm very interested in making Entity Framework 4 my ORM choice, if only because it:

  • Support for the first and first objects of the first object
  • Have a trusted LINQ provider
  • Be easier for customers (starting with Microsoft)
  • Come to the .NET platform instead of requiring 8 dlls to get up and running

In other words, are there any significant flaws for EF4?

Does it support all the basic NHibernate support functions (lazy loading, loading eagerly, level 1 caching, etc.) or is it still uneven at the edges? Is the syntax for setting mappings as easy as NHibernate and / or Fluent NHibernate?

Edit: Please do not raise your voice without trust. This was many years ago and addressed some of the serious flaws of EF1, which seem to no longer apply to EF4.

+6
orm entity-framework nhibernate
source share
1 answer

It seems that Ayende has a rather detailed blog post comparing the two, although he admits that this is not a thorough breakdown of the dots (which is kind of what I was hoping for here).

In general, I think that the points he raises in favor of NHibernate are valid, although a little on the good-to-have side. If, in fact, EF4 is actually missing, it seems that EF4 is a great alternative to NHibernate, if only for the reasons listed in the original question.

+3
source share

All Articles