I am not talking about performance or price.
I am talking about popularity.
Which is the most popular O/R-Mapper for .Net as of 2010?
Which would be the most popular O/R-Mapper for .Net for years to come?
I am not talking about performance or price.
I am talking about popularity.
Which is the most popular O/R-Mapper for .Net as of 2010?
Which would be the most popular O/R-Mapper for .Net for years to come?
NHibernate is most likely the biggest one right now, but MSEF is stealing its thunder (NH 3.0 has some major flaws in its Linq provider, and MSEF, though new, comes packaged with .NET 4.0)
If you include everything, i'd bet Linq to SQL is the most popular, but for large projects NHibernate i'd imagine.
I would venture to say that NHibernate is the incumbent, and presently most popular option. The current version (4.0 by name, 2.0 by "design") of Entity Framework (EF) has marked improvements over v1.0, which has issues that led many would-be adopters to adopt another solution, namely NHibernate, or roll their own.
As for the future, NHiberte has a solid following and is a mature product, whereas EF 4.0 needs to make amends for the many sins and shortcomings of the previous version, while still having its own issues, and being relatively young as a technology.
I would suggest that the ADO.NET Entity Framework has probably surpassed most other ORMs in popularity at this point, and will continue to grow faster than most in the future.
This is mainly because it's a supported part of the .NET Framework itself. LINQ to SQL predated it, so it may still (at this point) be more used, but most newer development seems to be switching over to EF, especially as it's getting a lot more attention from Microsoft.