Nhibernate, entity framework, active records or linq2sql?

If . NET 4.0, choose between Nbernate or Entity Framework. Nbernate is more extensible and generally more feature rich.

Entity Framework works better for firms that would rather have what Microsoft provides. They are both valid options and no one has yet published an objective significant blow by blow comparison. This is one of the better non-objective comparisons.

If . NET 4.0, choose between Nbernate or Entity Framework. Nbernate is more extensible and generally more feature rich.

Entity Framework works better for firms that would rather have what Microsoft provides. They are both valid options and no one has yet published an objective significant blow by blow comparison. This is one of the better non-objective comparisons: ayende.com/blog/archive/2010/01/05/nhibe... If .

NET 3.5 or earlier, choose N stackoverflow.com/questions/1238972/choo... stackoverflow.com/questions/567304/which... stackoverflow.com/questions/557948/easie... stackoverflow.com/questions/550929/some-... http://stackoverflow.com/questions/474973/best-orm-tool http://stackoverflow.com/questions/380620/what-object-mapper-solution-would-you-recommend-for-net http://stackoverflow.com/questions/249550/what-orm-frameworks-for-net-do-you-like-best http://stackoverflow.com/questions/206197/best-free-orm-tools-to-use-with-net-2-0-3-5 ayende.com/blog/archive/2010/01/05/nhibe...0 After September 04, 2009: ayende.com/blog/archive/2010/01/05/nhibe...1 http://stackoverflow.com/questions/1443846/o-rm-choice-not-reliant-on-linq http://stackoverflow.com/questions/1469761/nhibernate-vs-entity-framework-vs-something-better http://stackoverflow.com/questions/1470787/how-to-choose-an-object-relational-mapping-for-net That said, things change. Now that N I think Nbernate is the clear choice in the large majority of situations. For a longer and fairly up to date analysis, feel free to read this: .

NET and ORM - Decisions, decisions.

Also Code-First Entity Framework is great tool to design Business Domain Model and DAL for application: weblogs.asp. Net/scottgu/archive/2010/07/16/…. – URL1 Feb 24 at 15:16 This question has acquired some above average answers, even though it's a dup: stackoverflow.

Com/questions/5101974/comparison-entity-framework – Michael Maddox Feb 24 at 16:27.

My preference is LLBLGenPro - a really great ORM that just works like you'd expect. Its not based on configuration like entity framework or nhibernate, it generates your DAL based on your db (with much flexibility through their tools). llblgen.com/defaultgeneric.aspx.

LINQ2SQL is probobly easiest to use. Entity Framework provides great extensability and the future release will contain alot of improvements. One key rule for performance: write code that is easy to maintain, read and distribute; if it's to slow - optimize!

I think that the difference in performance between the ORMs today is bareley noticable, so you should pick the one that feels most comfortable and efficent to work with.

Entity Framework has better mapping of relationships than linq2sql (for example, it has multiple-multiple relationships). I haven't used the other two, but I used bernate in Java and it was pretty straightforward to use.

Could use PLINQO if you want many-to-many relationship support and use LINQ-2-SQL. Codesmithtools. Com/product/frameworks – Steven Rogers Apr 21 at 15:30.

This blog post compares various data technologies for . NET in various aspects (performance, maintainability, testability etc. ). Might be of some help to your decision making process.

1 That blog post is a little dated. Nbernate now has Linq support. The blog post doesn't mention Fluent N It doesn't look at LLBLGen or Subsonic, which both have decent mind share in the real world.

I have other minor nits, but in general, I disagree with the overly high scores that Entity Framework ended up with, especially pre-. NET 4.0. – Michael Maddox Sep 5 '09 at 15:19 Michael, SUbSonic isn't decent at all.

I really don't understand why people even try it. Just its 300 Kb assembly to e.g. 4 Mb @ OpenAccess - it must be clear it is just a tiny toy. And forget about LINQ there - I bet its LINQ support would never be even comparable to others.

– Alex Yakunin Nov 5 '09 at 21:54 Sorry, "SubSonic" and "Just its" => "Compare its" ;) – Alex Yakunin Nov 5 '09 at 21:55.

I face same dilemma. LINQ2SQL will give you more flexibility and immediate control over data access, however Entity Framework is the "enterprise" solution. I am currently trying this - SubSonic and look very promising.

To compare ORMs - take a look on ormbattle.net.

4 That site already has a very bad reputation. :( – Michael Maddox Sep 5 '09 at 15:13 Agreed, you have to look at which ORM company supports this website! – Codezy Sep 18 '09 at 22:02 Guys, visit FAQ and Blog @ ORMBattle, they explain a lot.

Michael, this site has bad reputation for you - I suspect because SubSonic you promote here shows its true face there. – Alex Yakunin Nov 5 '09 at 22:12 ORMBattle. Net is produced by one of the companies they "review" which, unsurprisingly, they rated highest.

– Mark A Mar 17 at 15:29.

My choice is Devart LinqConnect (devart.com/linqconnect/). This product as easy to use as LINQ to SQL (and even is compatible with it) and at the same time provides advanced ORM features like Entity Framework. I prefer their Visual Designer and their ORM features: Complex Types Lazy Loading PLINQ.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.