Book Image

Mastering Entity Framework

By : Rahul Rajat Singh
Book Image

Mastering Entity Framework

By: Rahul Rajat Singh

Overview of this book

<p>Data access is an integral part of any software application. Entity Framework provides a model-based system that makes data access effortless for developers by freeing you from writing similar data access code for all of your domain models.</p> <p>Mastering Entity Framework provides you with a range of options when developing a data-oriented application. You’ll get started by managing the database relationships as Entity relationships and perform domain modeling using Entity Framework. You will then explore how you can reuse data access layer code such as stored procedures and table-valued functions, and perform various typical activities such as validations and error handling. You’ll learn how to retrieve data by querying the Entity Data Model and understand how to use LINQ to Entities and Entity SQL to query the Entity Data Model.</p>
Table of Contents (19 chapters)
Mastering Entity Framework
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Using other Entity Framework approaches


In this chapter, we used the Entity Framework Code First approach to demonstrate how we can create a data-centric application using Entity Framework as the ORM. The reason for choosing the Code First approach is that this approach is the most verbose approach, and we get to see the code for all the entities.

If we were to use the Database First approach for this application, we just need to create the database that we saw in the beginning of the chapter, and add an Entity Data Model using the Database First approach. If we had used the Database First approach, our Entity Data Model would have looked like the following:

A generated Entity Data Model for the test application

If we want to use the Model First approach, then we need to use the Visual Entity Designer and create this model ourselves. The rest of the application code that we have seen would have remained the same even if we had used the database first or model first approach.

Tip

In larger applications...