We are setting up architecture in new project and it’s not easy to decide which DAL / ORM technology use in it.
NHibernate or Entity Framework ?
I’m determined to use NHibernate, but 2 of team members are familiar with EF and don’t now NH at all.

I was looking for post about NH vs EF, there are many (most of them are 1 year old) but only a few are recent , those recent ones are here:

• http://mattias-jakobsson.net/Item/32/Entity%20Framework%20vs%20NHibernate 
• http://gregdoesit.com/2009/08/nhibernate-vs-entity-framework-a-performance-test/ 
• http://gregdoesit.com/2009/08/nhibernate-vs-entity-framework-%E2%80%93-a-revised-performance-comparison/
• http://www.ilovenet.com.ar/2009-08-20/orm-performance-comparison/ 
• http://www.ormbattle.net/ 
• http://www.reddit.com/r/programming/comments/aeaos/nhibernate_vs_entity_framework_40_for_data/ 

UPDATE (05-01-2010):

First, we decided to use Entity Framework. After 2 weeks, we swiched back to NHibernate.
I’ll explain it in further posts, but main reason was buggy EF Designer in Visual Studio. It was hard & time consuming to build model.

Especially updating model from database was painful and buggy process.

Some few additional links:

• ADO.NET Entity Framework: Update Wizard will not add tables
  http://stackoverflow.com/questions/543971/ado-net-entity-framework-update-wizard-will-not-add-tables 
• What is the best practice when the database schema changes in entity framework?
  http://stackoverflow.com/questions/1900461/what-is-the-best-practice-when-the-database-schema-changes-in-entity-framework

My advice is: If you are creating enterprise application, don’t touch EF. Use NHibernate.
I’ve tested it.