http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660@Diego You actually missed Entity Frameworks biggest selling point: Its was made and is publicly endorsed by Microsoft.http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment16http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment16Mon, 28 Nov 2011 06:24:13 GMTHere's my comparison, which I did when I started with EF 4.1: http://stackoverflow.com/questions/5101974/net-orm-comparison/5105917#5105917 Now I would add that convention-based mappers for NHibernate (ConfORM, Fluent) are much more mature and flexible. EF's *ONLY* selling point is a more complete LINQ provider. Which, BTW, is not so great when you look at some of the horrible SQL it generates. Not to mention you can't pass entities to it (you need to pass the Id).http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment14http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment14Sat, 26 Nov 2011 16:18:50 GMTEF is just good enough.http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment13http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment13Sat, 26 Nov 2011 05:51:27 GMTOren, Did you marry someone from Microsoft? :-) I just finished a couple of Windows Phone projectsI & I missed NHibernate a lot since had to use Linq to Sql the only choice for Sql CE for WP7. I kind of agree with Jose; EF is very limited. I will not use that thing for anything serious at all. http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment12http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment12Fri, 25 Nov 2011 22:26:00 GMT@jose thanks for the review I tried the new EF CodeFirst and after all it is'nt that bad if you want to quickly achieve some simple basic things. For complex projects there is no other solution then NH at the moment and i don't know if the better LINQ support in EF is a real argument against NH since there are a lot of other ways for querying data. Documentation is always an issue and the reference at nhforge is not complete and needs a rework. For instance there is no word about the new ConfORM feature and how to use it. The other issue is support. Jose wrotes: "The experts of nhibernate will answer your question in minutes." In the last couple of months it is really hard to get an answer. I asked some questions with unit tests etc. but without any success. Fabio answered a lot of questions in the past, but since he moved back from the project it is really quite in the forum. But in the end there is alyways ligth and shade :-)http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment11http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment11Fri, 25 Nov 2011 10:13:36 GMTMost people who I found prefer EF of NH basically do so because Linq support is 'better'. http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment10http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment10Thu, 24 Nov 2011 22:39:46 GMTMy main production app was written with EF code-first. At first I loved it, but the more I use it the more "gotchas" I find. I don't really want to go through the whole thing and waste time replacing it with NHibernate (mostly since I used EF because there was better docs for learning EF4 than NH) but I definitely would use NH over EF for any new projects.http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment9http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment9Thu, 24 Nov 2011 14:09:06 GMTWith nuget there is no execuse for not using NHibernate either. Add package => nhibernate => donehttp://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment8http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment8Thu, 24 Nov 2011 14:08:58 GMTI wrote a detailed review of EF 4.1 CodeFirst RC vs NHibernate when this version came out. http://joseoncode.com/2011/03/30/entityframework-4-1-rc-code-first-review/ Basically, I won't use EF because is very limited, and for simple things I won't use NHibernate either just ado.net (maybe dapper because it has some nice extension methods).http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment7http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment7Thu, 24 Nov 2011 13:42:37 GMTI use EF when I'm in the mood to poke out my right eye. I use NHibernate when I'm in the mood to poke out my left eye. http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment6http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment6Thu, 24 Nov 2011 13:07:47 GMTIndeed NHibernate has more features and extension points, however sometimes you need to dive into the source code to find out the meaning of an interface method.http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment5http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment5Thu, 24 Nov 2011 11:21:15 GMTMathieu, Because EF is really limited in many of its capabilities.http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment4http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment4Thu, 24 Nov 2011 11:03:39 GMTThanks for this answer. "Mostly because I am able to do so much more with it." Do you think about your NHibernate knowledge vs your EF knowledge or do you think about some NHibernate features not supported by EF? If you think about features what are the top ones you think about?http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment3http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment3Thu, 24 Nov 2011 10:55:14 GMTMarc, Yes, I know, we are doing some work on RacconBlog now, will be fixed soonhttp://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment2http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment2Thu, 24 Nov 2011 10:35:43 GMTUnrelated to this post... your "Archive" (right hand bar) seems to be sorting by month number **as text**, hence Oct/Nov/Dec come between Jan and Febhttp://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment1http://ayende.com/137217/nhibernate-vs-entity-framework-usage#comment1Thu, 24 Nov 2011 10:28:58 GMT