Question

I would like to know what are the principal diferences between “ADO.NET Entitiy Data Model” and “Linq to SQL Classes”? What is the best choice to work with?

I couldn’t find any document on the internet explaing that and everything I know is that we can use both, “almost”, in the same way.

Answer 1

Linq To Sql is not being actively supported by Microsoft anymore.. They have picked the Entity framework has ‘the way for the future’. You can google and verify this.

Here’s your friendly neighbourhood SO topic with all the good bits

Update: Hmm.. it seems that MS has taken a step back from the infamous declaration. But the message is still not clear with respect to the future of L2S.

as of .NET 4.0, LINQ to Entities will
be the recommended data access
solution for LINQ to relational
scenarios.

We also want to get your feedback on
the key experiences in LINQ to SQL
that we need to add in to LINQ to
Entities in order to enable the same
simple scenarios that brought you to
use LINQ to SQL in the first place.

That pretty much reads ‘phasing out’ to me. I may be guilty of reading between the lines though.. there may be hope after all… behind all the ‘on-the-fence’ answers
ADO.Net team blog : Update on LINQ to SQL and LINQ to Entities Roadmap
ADO.Net team blog : Clarifying the message on L2S Futures.
http://damieng.com/blog/2008/10/31/linq-to-sql-next-steps