Clever Geek Handbook

What strategy should be adopted now that MS no longer supports LINQ to SQL?

Please, if you've used NHibernate and Entity Frameworks, please compare your experience.

+1


source to share


2 answers


We were early LINQ to SQL users, but only on a limited basis, waiting for the Entity Framework. We've just started with EF, but my biggest complaint is still the same as mine with LINQ to SQL as my domain model is still married to either a data source or a framework, which means my POCOs are not truly independent as they should be.

Of course, on the Entity Framework Design blog, they admitted that ignorance of persistence is a very popular feature requested (and will be in the next release), and there is at least one example of how to achieve ignorance of persistence when using real POCOs here .



We also rated NHibernate. It is very durable and easy to use. Realistically, other things being equal, NHibernate is better installed, but I have a personal preference to stick with Microsoft implementations unless I have a legitimate reason - if not for any other reason other than the level of quality of support I can get.

+3


source


You can also consider Castle ActiveRecord , which is a layer on top of NHibernate. In my opinion, this does the whole ORM thing.



+3


source






More articles:


All Articles