I came across this article at :
http://redmondmag.com/news/article.a...orialsid=10472
and also TIm's blog at:

http://blogs.msdn.com/adonet/archive...s-roadmap.aspx

"If Microsoft is serious about Entity Framework being the preferred
data-access solution in .NET 4.0," They'll have to do a few things: Make EF
2.0 rock-solid.
Can you explain to us why EF is needed.
What is the problem that Entity Framework is solving?
Why is Entity Framework a better solution to this problem?"
Any ideas whay we are getting to?

Yep, LINQ to SQL is dead.
EF, well, it is an ORM, not the best one though. One of the better sides is
LINQ support.

There is a lot of documentation on ORM (object relational mapping) on the
web, just do some searching and you'll understand why one would use ORM
(perhaps EF).

--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

"Patrick.O .Ige" <(E-Mail Removed)> wrote in message
news0AB9D9D-32BF-4BA5-AF4C-(E-Mail Removed)...
>I came across this article at :
> http://redmondmag.com/news/article.a...orialsid=10472
> and also TIm's blog at:
>
> http://blogs.msdn.com/adonet/archive...s-roadmap.aspx
>
> "If Microsoft is serious about Entity Framework being the preferred
> data-access solution in .NET 4.0," They'll have to do a few things: Make
> EF
> 2.0 rock-solid.
> Can you explain to us why EF is needed.
> What is the problem that Entity Framework is solving?
> Why is Entity Framework a better solution to this problem?"
> Any ideas whay we are getting to?