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? ;-)