tags:

views:

249

answers:

2

I would like to see your experience with popular ORM tools outhere, like NHibernate, LLBLGen, EF, S2Q, Genom-e, LightSpeed, DataObjects.NET, OpenAccess, ...

From my exp: - Genom-e is quiet capable of Linq & performance, dev support - EF lacks on some key features like lazy loading, Poco support, pers.ignorance... but in 4.o it may have overcome .. - DataObjects.Net so far good, althrough I found some bugs - NHibernate steep learning curve, no 100% Linq support (like in Genom-e and DataObjects.Net), but very supportive, extensible and mature

+4  A: 

http://www.ormbattle.net/

THat is about the best comparison you can find at the moment.

From my experience, btw.: Stay AWAY from NHibernate current release if you have interest in LINQ - use the development branch. The LINQ support mvoes into the main DLL AND - more important - is a lot better and complete than the limited add on methods in the current releases.

TomTom
ormbattle.net is not really a good way to evaluate differenct Orm tools as the that benchmarking is kind of useless in production code.
@TomTom: I believe the ormbattle.net is same as http://ormeter.net!
KMan
depends. At least it ALSO gives you features. For example you can see whether implementations of for example LINQ features are good or bad. Many of the benchmarks are feature tests.
TomTom
On orm battle the best tool is project, where you need to write all required SQL in attributes for objects. Do you think its a good ORM?
Sly
@Sli: depends on what you want do.. the DO.Net is DDD driven or 'code first' driven, so using it for some Legacy DB is maybe not suitable..
+2  A: 

http://ormeter.net/

alt text

KMan
thank you for the chart but I already saw this site weeks ago.. I wanted to know personal experience not some diagnostics on synthetic benchmarks
That won't work. Seriously - personal experience is very personal on personal project demands. Some people work perfectly with LINQ, but most of the time if you ask behind it is because they dont have a clue what a ORM is capable of acutally, and are totally happy to ahve something better than crappy handwritten stuff.
TomTom
you still can have a good experience with an ORM (bug-free, good functionality, support) and a bad experience (too many bugs, crappy functionality, delayed (or even none!) support from company/community.. so IMHO I think this is a valid question.