Book Image

Entity Framework 4.1: Expert's Cookbook

By : Devlin Liles , Tim Rayburn
Book Image

Entity Framework 4.1: Expert's Cookbook

By: Devlin Liles , Tim Rayburn

Overview of this book

<p>Entity Framework 4.1 allows us to dive into the world of data access without having to write SQL statements. With the power to shape data access by your object model comes questions and this book holds the answers.</p> <p>Entity Framework 4.1: Expert's Cookbook holds many examples to help guide you through tough technical decisions and avoid technical landmines. The book will guide you from just using Entity Framework to enhancing the data access wizard.</p> <p>This book starts with examples that require some familiarity of object relational mappers, and then moves on to more advanced tasks. You will be guided through complex mapping scenarios, query definition, reusability, integration with other technologies, and architectural management. The approach is step-by-step and test driven so that it is focused as much as possible on solving problems and getting the most out of the time spent working through the book.</p> <p>Entity Framework 4.1: Expert's Cookbook is a must have for any .NET developer who uses Entity Framework, and wants better, cleaner, and more maintainable code.</p>
Table of Contents (15 chapters)
Entity Framework 4.1: Expert's Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Introduction


Have you ever tried to explain the unified field theory to someone that has no understanding of physics? We would have to tell them about the ideas of Einstein on how the universe was put together, and how the basic physic particles interact. If they have not fallen asleep by this point, we then have to explain even more things that are the final details. These details are required for the explanation of theory, but not everyone is interested in them. This is much like what the storage schema in a database means to object-oriented programmers. They have to worry about it at some point, but it will never be their focal point in the way that it is for a database administrator. When we say that the two objects are related, we think something completely different from a database administrator who hears the same phrase. When we try to convey our ideas to someone, it often helps to put them into terms that the other person can understand and relate to. This is not so different from...