Hello,

I've noticed that the book's db related examples focus mostly on LINQ To SQL, yet Microsoft has announced that Entity Framework (EF) is taking its place. From that announcement, I assumed that Microsoft developers were expected to adopt EF instead of LINQ To SQL.

Why was the choice made to use LINQ To SQL in this book instead of Entity Framework?

Thanks
Mark

I assumed it has something to do with the time lap.

Entity is relatively new, compared to LINQ to SQL (not exactly an old timer either). And books and the codes that come with it, tend to be 1 year behind.

Just look at the MVC, most books on it don't even start to appear until June this year at the latest.

You pointed out a problem for everyone, what to learn or catch up that will not be wasted later? :).

How about a Wrox Blox update, Jim?

__________________
Alex

- TheBeerHouse Mods Repository
http://www.sashka.com/TheBeerHouse/thebeerhouse.html

And how about an Entity Framework book from Wrox? ;-)

suggest me the best for an asp.net and oracle application. i am currently using Entity framework.

Geomar, I am currently going through the ASP.NET MVC 2 book (with NerdDinner) trying to use EFv1. The first EF version was not ready for prime time; tasks that were simple in LINQ to SQL are major issues in EFv1. Such as mapping a database scalar-valued function.

From Wikipedia:

Version 1 of Entity Framework (EFv1) was included with .NET Framework 3.5 Service Pack 1 and Visual Studio 2008 Service Pack 1, released on 11 August 2008. This version has been widely criticized, even attracting a 'vote of no confidence' signed by several hundred developers.

The second version of Entity Framework, named Entity Framework 4.0 (EFv4), was released as part of .NET 4.0 on 12 April 2010 and has addressed many of the criticisms made of version 1.

A third version of Entity Framework, yet unnamed, is planned for release in first quarter of 2011. There have been several betas (called Community Technology Preview) of it and the last CTP5 was released in December 2010.