Choosing Entity framework as default implementation ORM against Nhibernate, cons and pros?

Nobody can answer this question. I believe even ADO.NET team would have problem with this because at this time there is even no road map for features that will be implemented in the future. At the moment the development process is mostly driven by Data UserVoice and there is no way to know which features we can expect next month, which features we can expect next year and which features we will never have.

I would recommend that, in making your decision, you concentrate on the features available from NHibernate and EF right now. Look at the precise requirements you have to hand and match them up against the ORMs. In your question above, you should note that it is also possible to execute linq queries against NHibernate.

Also, you've discounted the need for 2nd level caching. If you are looking for a long-term flexible platform, you should definitely take it into account.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.