How to choose that which ORM would be feasible for or Application? e.g if we are using Linq then why not hibernate

How to choose that which ORM would be feasible for a web Application? 开发者_StackOverflow中文版e.g if we are using Linq then why not nhibernate? and Which one is better and why

Every ORM that claims linq support, supports linq to a degree, however the completeness of the implementations vary greatly, sometimes because of the way the ORM is implemented, sometimes because of the quality of the Linq implementation.

Even the Linq implementations between Linq to Sql and Entity Framework v4 vary greatly, if you then look at NHibernate's or LlblGenPro's implementations you will find there are queries that are possible in sql that each doesn't support in the same way, if at all, or that the support with different levels of efficiency.

You really need to evaluate the particular ORM's Linq implementation against the type of data retrieval you tend/want to do.

I think a lot would depend on the application you are building.

On the other hand, NHibernate is very powerful and can be customized to do just about anything. We recently dumped our old ORM and moved to NHibernate because we just couldn't do what we needed to do without it.

You can use Linq with nHibernate. But take the most popular ORM. The one the most developers use.

It will be easier to find a developers to maintain and enhance the project and it will be easier to find solutions to your problems on Google.

I'm still using nHibernate but new versions of Entity Framework look promising.

I will switch when Entity Framework will become as powerful as nHibernate.