LINQ to SQL -vs- LINQ to Entity

LINQ to SQL -vs- LINQ to Entity

Old forum URL: forums.lhotka.net/forums/t/5730.aspx


CyclingFoodmanPA posted on Tuesday, November 04, 2008

Ok, I just downloaded the 3.60 beta 2a stuff and noticed the Project tracker has a .dbml file and an .edmx file and I am trying to figure out what part of the code utilizes the EF code.  I notice the Roles table is in the .edmx file but the Roles.cs file utilizes the DalLinq file.  Is there going to be a complete ProjectTracker example that utilizes the EF so we can compare and contrast LINQ to SQL and LINQ to Entity implementation?  I was just getting LINQ to SQL down and noticed a blog indicating that the ADO.NET team is going to slow down work on L2S and move forward on L2E. 

It is ok as I have not finalized my Data Access method yet but I need to decide fairly quickly and I am using a product called CodeComplete and I also emailed Philip and asked if they are going to move to L2E.  So, a number of questions are in the mill now. 

So, is there going to be a ProjectTracker app utilizing entierely L2E to check out.

Keith

RockfordLhotka replied on Tuesday, November 04, 2008

I did this while writing the book - chapter 18 specifically - and due to time pressures I was simply unable to complete a full EF-based implementation. The book uses an L2S DAL, as shown in the 3.6 code.

My primary roadblock with EF is its limitations around stored procedures. It is just radically harder to use than L2S in this regard :(

However, if you've been watching the blogosphere you are aware that Microsoft has given the nod to EF now, so you can expect that 3.6.1 or 3.6.2 will probably switch over to EF.

It is all dependent on my schedule of course, and right now all my energies are going toward getting the book out in a timely manner, and supporting Joe in getting the VB book out shortly after.

CyclingFoodmanPA replied on Wednesday, November 05, 2008

Thanks Rocky,

They (Microsoft) need to slow down so you can get some breathing room!  One thing I know for sure, sprocs are fast and efficient and I am battling with what technology to use.  But, you mentioning that EF has limitations on sprocs is a major road block for me and I may just stick with either pure ADO.NET sprocs or L2S.

Thanks for all your hard work Rocky in developing an awesome framework.

Keith

 

 

 

Copyright (c) Marimer LLC