You are currently viewing the BOOK: Professional ASP.NET MVC 1.0 ISBN: 978-0-470-38461-9 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
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?
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.
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.