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

Entities, entity types, and relationships in the EDM

The EDM is an implementation of the Entity-Relationship model (commonly called the E-R model). It depicts entities and their relationships. The EDM is a view of the data store that your application will use.

Before we explore deeper into our Security DataModel, let's discuss entities, entity types, relationships, and how these are all represented.

What is an entity?

An entity essentially models individual, real-world objects such as employees and customers. Such objects contain information pertaining to the entity. An entity is something that is uniquely definable, distinctly identifiable, and can have one or more of the following properties:

  • It should be identifiable easily through the data that it holds

  • It should have properties that can hold scalar values that represent the entity's data

  • It should only contain data, not methods or operations on the data

  • It can have entity relationship information such as how one entity is related to another...