Book Image

Entity Framework Core Cookbook - Second Edition

By : Ricardo Peres
Book Image

Entity Framework Core Cookbook - Second Edition

By: Ricardo Peres

Overview of this book

Entity Framework is a highly recommended Object Relation Mapping tool used to build complex systems. In order to survive in this growing market, the knowledge of a framework that helps provide easy access to databases, that is, Entity Framework has become a necessity. This book will provide .NET developers with this knowledge and guide them through working efficiently with data using Entity Framework Core. You will start off by learning how to efficiently use Entity Framework in practical situations. You will gain a deep understanding of mapping properties and find out how to handle validation in Entity Framework. The book will then explain how to work with transactions and stored procedures along with improving Entity Framework using query libraries. Moving on, you will learn to improve complex query scenarios and implement transaction and concurrency control. You will then be taught to improve and develop Entity Framework in complex business scenarios. With the concluding chapter on performance and scalability, this book will get you ready to use Entity Framework proficiently.
Table of Contents (15 chapters)
Entity Framework Core Cookbook - Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Generating entities from the database


Entity Framework Core 1.0 supports two different workflows:

  • Code first: Entities are first generated as code and only then is the database generated. This follows the Domain Driven Design (DDD) approach.

  • Database first: We already have a database and we want to generate entities for it.

The first approach was made popular when Entity Framework 4.1 "Code First" was released. The idea here is that we, as C# developers, understand code better than anything, and so we model our entities as code. It is left for Entity Framework to produce the database objects (tables, relations, and so on) that will enable it to persist our data in an almost transparent way.

But what happens when you have an existing (legacy or otherwise) database, perhaps consisting of hundreds of tables? Or you have this super cool UML tool that generates the database from a model? It is troublesome, to say the least, to generate all C# entities by hand in Visual Studio, so the option is...