By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
439,972 Members | 1,454 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 439,972 IT Pros & Developers. It's quick & easy.

linq to sql or ado.net entity framework?

P: n/a
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?

Oct 22 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Andy B" <a_*****@sbcglobal.netwrote in message
news:uQ**************@TK2MSFTNGP06.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

Oct 22 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.