Other Sellers on Amazon
Order now and we'll deliver when available. We'll e-mail you with an estimated delivery date as soon as we have more information. Your account will only be charged when we ship the item.
+ $3.00 Delivery
88% positive over last 12 months
+ FREE Delivery
Delivery rates Return policy

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required. Learn more
Read instantly on your browser with Kindle Cloud Reader.
Using your mobile phone camera, scan the code below and download the Kindle app.

Entity Framework 4.0 Recipes: A Problem-Solution Approach Paperback – Illustrated, 6 May 2010
Larry Tenny (Author) Find all the books, read about the author, and more. See search results for this author |
Zeeshan Hirani (Author) Find all the books, read about the author, and more. See search results for this author |
Enhance your purchase
- Getting Started With Entity Framework
- Entity Data Modeling Fundamentals
- Querying an Entity Data Model
- Using Entity Framework in ASP.NET
- Loading Entities and Navigation Properties
- Beyond the Basics with Modeling and Inheritance
- Working with Object Services
- Plain Old CLR Objects
- Using the Entity Framework in N-Tier Applications
- Stored Procedures
- Functions
- Customizing Entity Framework Objects
- Improving Performance
- Concurrency
- Advanced Modeling
- Print length648 pages
- LanguageEnglish
- PublisherApress
- Publication date6 May 2010
- Dimensions20.32 x 3.71 x 24.77 cm
- ISBN-101430227036
- ISBN-13978-1430227038
Product description
About the Author
I’d like to read this book on Kindle
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
Product details
- Publisher : Apress; 1st ed. edition (6 May 2010)
- Language : English
- Paperback : 648 pages
- ISBN-10 : 1430227036
- ISBN-13 : 978-1430227038
- Dimensions : 20.32 x 3.71 x 24.77 cm
- Customer Reviews:
About the authors
Discover more of the author’s books, see similar authors, read author blogs, and more
Larry Tenny has more than 20 years of experience in developing applications using a broad range of development tools primarily targeting the Microsoft platform. He has extensive .NET development experience and a Ph.D. in Computer Science from Indiana University in the United States.
Zeeshan Hirani is a longtime .NET and database developer. He currently works at a top Internet e-commerce site where he is involved in Microsoft technologies like Entity Framework,LINQ TO SQL,ASP.NET and Silverlight.He has extensive experience with many ORM and database technologies, which provides him with a unique perspective on Microsoft's Entity Framework. He has written several articles, maintains an influential Entity Framework blog, and is a frequent contributor to many .NET forums. He is a Microsoft MVP.
He has a Bachelors in Information Systems and is currently getting his MBA from University of Dallas.
For more updates on his work, visit his blog at below address..
http://weblogs.asp.net/zeeshanhirani
Customer reviews
Top reviews from other countries

While some comments noted that there is some confusion in presenting both a LINQ and Entity SQL solutions I suspect their intent was to provide solutions for those already familiar with LINQ as well as a solution in Entity SQL for those who have never been exposed to it. For those unfamiliar with either technique, I think the code speaks for itself: to me it's obvious that Entity SQL is simply more concise, "tighter" in terms of verbiage and clearer in its intent; more intuitive. Those more familiar with LINQ might disagree, but then, that's why the solutions are presented using both techniques: your choice. As for "confusing," or which one's "right," both work equally well, and are nicely contrasted with one another. I'd venture, however, that the MS future is evolving towards Entity SQL and away from LINQ; clearly that's where development is ongoing. So be it.
Clearly, Entity Framework is an evolving technology. This book address the future where "a database" may in fact only be a metaphor for a multitude of storage mechanisms and devices physically dispersed and diverse. EF handles that through the conceptual model, and this book gives you techniques for communicating with that conceptual model; MS handles all the rest. The complexity of diverse storage is sidestepped, or more to the point, simply ignored, as the code examples in the book simply and elegantly demonstrate communication with the conceptual model. For those looking towards the future of communicating with data, I highly recommend this book.

The authors of this book are definitely among them.
I have only a very brief hands-on exposure to EF (Entity Framework), and it was for .NET 3.5.
Among other things, I had to change the foreign key values in a self-referencing SQL Server table so that the foreign key now "points" to another primary key. It's very similar to the classic example of moving an entire subtree in a hierarchy structure under another "parent" (into another subtree).
The project was on an extremely tight schedule, and after wasting an hour or so trying to figure out the EntityKey stuff, I gave up and used good old classic ADO.NET (SqlConnection, SqlCommand, etc.).
The problem was caused by one of the very annoying deficiencies in EF 3.5, which were fixed by Microsoft in the EF 4.0 (.NET 4.0) release, along with quite a few other improvements.
Essentially, EF is a very compelling replacement for "classic" ADO.NET, and even for the not-so-old LINQ-to-SQL.
This book contains a lot of short concise "recipes" for practically every conceivable "real-world" situation you might have when using a database from .NET.
Needless to say, it has an example for my situation (described above), too.
Unlike most other technical books, this one has a much more practical structure:
1. A short Chapter 1 gives you an overview of the basic concepts and principles of EF 4.0.
2 - ... and then you jump right into writing real code!..
You can use this book as a manual for a thorough study of Entity Framework 4.
And/or, you can use it as [probably, the best] reference material for your own project challenges.
Each recipe is only a few pages long (mostly, code snippets), and it contains just enough theory for a novice to understand the code sample.
At the same time that the book can be used as a reference, it also walks you through the entire EF from simple stuff to more complex and less-often used scenarios.
So far, I'm approximately 1/4 through the book, and I can't stop reading it. By the way, it's also a very easy read.
I would have given this book 10 stars, but regretfully, 5 is the maximum.
My recommendation: if you are a .NET developer, get this book. You'll love it.

This book is an exception to that rule, partially because EF 4.0 is so simple to use that you really don't have a huge mystery hanging over you as to what's it's there to do. But indeed, there are lots of little things that you can do to make the experience much better. This book shows those tweaks and explains them well.
The book appears to be well organized, in that the examples start off with what would be the most common problems encountered. Then it moves on into more complex stuff as you read. The authors clearly have a command of EF 4.0 and did a good job on this book.
Buy it!

However EF4.0 gives you ability to map your objects to part of the table or to multiple tables. It shows you how inheritance can be represented in database.
Even if you not going to use EF in your working environment, still this book gives you a lot of ideas and best practices to think of.

I must admit I am more a theory kind of guy and prefer to know how things work thus I am able to resolve new problems as they might arise. I also know that sometimes knowing all of the theory can be bad in the sense that it takes longer to get some work done while learning.
I have walked away from this book with more questions about the EF and data modeling than I started with. Yes I have new knowledge of EF and modeling but I wonder how correct it is. Trying to infer the real meaning of these new (to a coder) data modeling patterns from a click here, drag there type experience leaves me wondering.
I would suggest a book that covers more theory prior to this if you are new to the EF.