Linq-to-SQL or Linq-to-Entities with ASP.NET 3.5 and SQL Server 2005 -

I am starting a new project using SQL Server 2005 with C # and ASP.NET 3.5, and I I am trying to decide which ORM is best to use between LinqToSQL, LinqToEntities, or NHibernate.

Ideally I would love to use Microsoft's best practice; But I need to use a solution that will provide comparable performance for using stored procedures without maintenance overhead, and deploying updates from web applications and databases will be easy as we are in an enterprise enterprise and the database is used by other groups Is controlled.

I think LinqToSQL provides that the ease of use, and I am leaning towards a Linq solution on NHibernate

Jason

If you're looking for "Favorite Microsoft's Best Practices" then you want to go with the unit framework (Lin-to-Entites) Are there. Microsoft has said that they are focusing their efforts on ORM. LINQ to SQL (I do not think) is being actively developed, in addition to maintenance and security improvements.

My personal opinion is that with small, simple projects LINQ is to go with SQL. I like to use EF in big and strong applications.

NHibernate is also a very good solution, and has LINQ provider, so you can also check it (if notified well for any other reason). But for me, I have to be in 'official' Microsoft solutions.