linq to sql or ado.net entity framework?

[Andy B]

I have to learn how to do one or the other: linq to sql or ado.net entity
framework. There will be overhead no matter what way I go since I don't know
either one. Which one would be the best one to use overall?

[John Saunders]

"Andy B" <a_*****@sbcglo bal.netwrote in message
news:uQ******** ******@TK2MSFTN GP06.phx.gbl...

I have to learn how to do one or the other: linq to sql or ado.net entity
framework. There will be overhead no matter what way I go since I don't
know either one. Which one would be the best one to use overall?

I would learn Entity Framework. LINQ to SQL is meant to be a one-to-one
mapping to your database. OTOH Entity Framework gives you the flexibility to
have an entity model that works in your code at the same time as a database
model that works in the database.

One example is that you can do inheritance. You can have a "Person" entity
that both "Employee" and "Customer" entities derive from.

--
John Saunders | MVP - Connected System Developer