Please if you have used NHibernate and Entity Frameworks, please contrast your experiences.
Please if you have used NHibernate and Entity Frameworks, please contrast your experiences.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Please if you have used NHibernate and Entity Frameworks, please contrast your experiences.
We were early adopters of LINQ to SQL, but only on a limited basis while waiting for the Entity Framework. We have only started working with EF, but my largest complaint is still the same one that I had with LINQ to SQL, being that my domain model is still married to either the data source or the framework, meaning my POCOs are not really as independent as they should be.
Of course, on the Entity Framework Design blog, they have recognized that persistence ignorance is a very popular requested feature (and will be in the next release), and there is at least one example of how to achieve persistence ignorance while using true POCOs here.
We also evaluated NHibernate. It is very solid and easy to use. Realistically, with all other things being equal, NHibernate is better established but I have a personal preference to stick with the Microsoft implementations unless I have a legitimate reason not to – if for no other reason than the quality level of support I can get.