Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m well aware that similair topics have been brought up before
e.g. Entity Framework 4 vs NHibernate
But instead of arguments like:
I would like to see a more detailed list of features that you consider missing from EF4.
Personally, I think the lack of enum support is the biggest drawback of EF4.
Ayende did a good work of listing NHibernate advantages over EF here: http://ayende.com/blog/archive/2010/01/05/nhibernate-vs.-entity-framework-4.0.aspx
In a nutshell, NHibernate contains many more ways to improve performance in real world scenarios than EF4 (batching being the most obvious), and more flexibility and extensibility pretty much everywhere.