Linq to SQL

I do not think that EF is much harder than L2S, at least not for common tasks and 1-1 table to class implementation, or even parent-child list-grandchild list scenarios.  It becomes a problem when your DB does not correspond directly to classes (you are constructing a class from data in two tables), but the same issue exists in L2S as well.  There is also no option for eager loading on context level – you have to do this as part of Linq query.  There is also a helper class to manage data context for EF as well in 3.6.

Sergey Barskiy

Principal Consultant

office: 678.405.0687 | mobile: 404.388.1899

Microsoft Worldwide Partner of the Year | Custom Development Solutions, Technical Innovation

So it seems pretty clear; L2S is on the way out.  It's a shame.. I haven't looked at EF so far, but it sounds a lot more complicated than L2S.  And I just finished replacing my custom ORM with L2S.  *sigh*