1

I am trying my best to understand what is the difference between "ADO.NET - Entity Data Model" and "LINQ To SQL", but I cannot figure it out. Can someone please explain the differences between the two and the advantages and disadvantages?

Thanks Frank

Improve this question

2 Answers 2

Reset to default
2

Linq to SQL was actually a proof of concept for Linq. See The Origin of LINQ to SQL. Microsoft is putting its weight behind Entity Framework, although I believe it's not quite ready for prime time.

Anyway, this StackOverflow post provides some additional detail about the differences.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

Linq to SQL is said to be dead (I don't think so though - it was way to well received by the development community). Entity Framework is its successor, if you want. It can access more data sources (more database types, and also different kinds of sources such as reporting services, business intelligence etc.). It's much more complex than Linq to SQL, and has a steeper learning curve, for example EF allows one class-multiple tables mapping. Other things are not possible with EF, such as specifying deferred loading - that's Linq to SQL only.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.