Book Image

Entity Framework Tutorial (Update) - Second Edition

By : Joydip Kanjilal
Book Image

Entity Framework Tutorial (Update) - Second Edition

By: Joydip Kanjilal

Overview of this book

The ADO.NET Entity Framework from Microsoft is a new ADO.NET development framework that provides a level of abstraction for data access strategies and solves the impedance mismatch issues that exist between different data models This book explores Microsoft’s Entity Framework and explains how it can used to build enterprise level applications. It will also teach you how you can work with RESTful Services and Google’s Protocol Buffers with Entity Framework and WCF. You will explore how to use Entity Framework with ASP.NET Web API and also how to consume the data exposed by Entity Framework from client applications of varying types, i.e., ASP.NET MVC, WPF and Silverlight. You will familiarize yourself with the new features and improvements introduced in Entity Framework including enhanced POCO support, template-based code generation, tooling consolidation and connection resiliency. By the end of the book, you will be able to successfully extend the new functionalities of Entity framework into your project.
Table of Contents (16 chapters)
Entity Framework Tutorial Second Edition
About the Author
About the Reviewers

Creating a database using model-first development

One of the most interesting new features and enhancements introduced in Entity Framework 6 is its ability to generate a database from an existing object model. This approach provides you with better control over your design and promotes domain-driven design (DDD). In this approach, you can design your domain model based on the business requirements first and then generate the database from it.

Before we explore this further, let's take a quick tour of the modeling approaches that are supported. The domain modeling approaches in Entity Framework include the following:

  • Code-first: In this approach, the domain model is first defined using the POCO classes and then the database is created from these classes. This approach is popular and provides much more control over your code—you just need to define the database mappings and leave the creating of the database entirely to Entity Framework. Note that as your code drives the database, manual changes...