Book Image

Code-First Development with Entity Framework

By : Sergey Barskiy
Book Image

Code-First Development with Entity Framework

By: Sergey Barskiy

Overview of this book

<p>Entity Framework Code-First enables developers to read and write data in a relational database system using C# or VB.NET. It is Microsoft's answer to demand for an ORM from .NET developers.</p> <p>This book will help you acquire the necessary skills to program your applications using Entity Framework. You will start with database configuration and learn how to write classes that define the database structure. You will see how LINQ can be used with Entity Framework to give you access to stored data. You will then learn how to use Entity Framework to persist information in a Relational Database Management System. You will also see how you can benefit from writing ORM-based .NET code. Finally, you will learn how Entity Framework can help you to solve database deployment problems using migrations.</p>
Table of Contents (15 chapters)
Code-First Development with Entity Framework
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Summary


In this chapter, you learned how to issue basic queries to retrieve entities from a database. LINQ was the driving force behind getting the data from the database through Entity Framework. There are two basic approaches to using LINQ: the method and query syntaxes. The query syntax is quite similar to SQL, whereas the method syntax may be more suitable for developers with more experience in C# or VB.NET than SQL. We saw how to use both approaches to filter data. We saw that the where clause can be used to combine multiple conditions using logical operators. The ordering of data can be done as well, using either the OrderBy and OrderByDescending methods or ascending or descending keywords. In order to support multiple orders by conditions, we can use the ThenBy method. What we retrieved from the database were entities that were mapped to tables. We often do not need to think about this; simply assume that the Entity Framework persistence engine is taking care of these nitty-gritty...