Editor's Notes

1. Projecting: L2S can project to a structure. EF can't (run time exception) (see http://www.thedatafarm.com/blog/2008/08/15/AFewThingsYouCantDoWithEFQueriesWhichYouWontFindOutUntilRuntime.aspx)
2. Both frameworks have similar implementations for selecting collections of objects from stored procsFor POCO Objects – L2S can fetch using ExecuteCommand and will map the fields from the return type to the object type supplied. Missing or additional columns are ignored. EF doesn’t support POCO with V1.Multiple Results – L2S can handle multiple results but they must be coded manually. EF doesn’t have support for multiple results, but see the EFEXtensions library for a solution. Also see http://blogs.msdn.com/meek/archive/2008/03/26/ado-entity-framework-stored-procedure-customization.aspx. Scalar results – L2S can auto-map. EF requires manual mapping.Executing without results – L2S uses ExecuteCommand, EF requires creating ADO code as extension method of the context using ExecuteNonQuery
3. EF:Final projection must be an entity type that has the correct association and it can’t be modified along the way (Group By) see http://wildermuth.com/2008/12/28/Caution_when_Eager_Loading_in_the_Entity_Framework