Entity Data Model (EDM) in-depth analysis, Part 1

The Entity Data model is a new feature introduced in the. NET Framework v3.5 SP1, a more powerful ORM than LINQ to SQL, allowing developers to focus only on the development of the domain object model without considering how they interact with relational databases. This series of articles delves into the following: EDMX Schema files, Model Browser, mapping relationships, resulting entity classes (generated entity classes), documentation (documentation), and more.

1. EDMX Schema File

You can open EDMX as an XML file, and you'll find that the file contains 3 main sections.

Conceptual Models (CSDL)

Storage Models (SSDL)

Mapping (MSL)

In general, you do not need to manually modify the Edmx-xml file. The visual EDM Designer, Mapping Details window, and Model Browser window contain these 3 parts and are very friendly to display the entire entity Data model.

When you compile the project, MSBuild extracts the CSDL/SSDL/MSL content from the edmx file and places 3 separate XML files into the project's output directory.

2. Model Browser window

The Model browser window displays the conceptual model and the storage model visually tree.

3. Mapping Details window

The EDM Designer also provides a nice mapping Details window that contains 2 views.

Map Entity to Tables/view

This view shows the properties in all fields and corresponding entities in the database that you can use to view and edit the mapping relationships of the EDM.

Map Entity to functions

This view is used to select a particular stored procedure to insert, UPDATE, or delete the entity instance.