ADO.NET Entity Framework vs NHibernate

Question

Thus, the Entity Framework ADO.NET got a little bad press (in the form of blog entries and a petition), but I do not want to rush to judgment. I am limited in time for experiments, but I was wondering, did anyone work with him with even more empirical feedback?

Finally, what we think about using NHibernate, which has been around for a long time and may be more mature than the ADO.NET Entity Framework.

Answer 1

NHibernate may be more mature. This does not necessarily mean that it is the “best” solution. Using it at my work for some time, I personally would prefer to use almost everything than NHibernate (even direct SQL if migration was a remote feature). The number of error messages generated by NHibernate that mean nothing (or mean something, but should never happen) is absolutely staggering, as are some of its default behavior (for example, clears the session once for each object returned in Find).

Personally, when I have a choice, I use LINQ to SQL to work with the database.

Answer 2

If null configuration is the main advantage of SubSonic, you can look at Free nHibernate or Entity Framework Code-First

UPDATE of Răzvan Panda: Fluent NHibernate is deprecated in most cases by enabling code display in NHibernate itself, see notherdev.blogspot.ie/2012/02/

Answer 3

It has been 2 years since publication. From what I understand, the ADO.NET Entity Framework has matured with .net 4. Does anyone have any new feedback on this topic?

Here's a link to improvements added to EF since its first release in 2008 http://blogs.msdn.com/b/adonet/archive/2009/05/11/update-on-the-entity-framework-in-net- 4-and-visual-studio-2010.aspx

Update: I found this thread on stack overflow, which discusses the updated EF pretty well:

Entity Framework 4 vs NHibernate

Answer 4

Microsoft has all recognized that the ADO.Net Entity Framework is not an ORM (I cannot find the link at this time). Therefore, if you think of the Entity Framework as a query mechanism, then it seems to be really good at what it does. For a complete ORM solution, you might want to look elsewhere.

The following blog post seems to confirm this difference:

http://blogs.msdn.com/dsimmons/archive/2008/05/17/why-use-the-entity-framework.aspx

Answer 5

I used SubSonic, LinqToSql, LinqToEntities. Now I'm trying NHibernate. At the moment - I like NHibernate (probably because I did not satisfy the problems enough). The worst of them is LinqToEntities (this is just my opinion, of course).

Answer 6

I have a problem with SubSonic. SubSonic suffocated from tables with the same name, but with a different scheme. I do not want to discuss the best practices of creating a database because I did not call to do this. (When it comes to raising your voice, make a bet and do this work, I would rather keep my work.))

Answer 7

I come to sympathy for Entity. It takes some time to understand what all of his error messages mean, but once you get used to it, this is really great work. The biggest flaw he has now is not real support for disconnecting.