Entity Framework Tutorial Basics（5）：Create Entity Data Model

Create Entity Data Model:

Here, we are going to create an Entity Data Model (EDM) for SchoolDB database and understand the basic building blocks.

Entity Data Model is a model that describes entities and the relationships between them. Let's create first simple EDM for SchoolDB database using Visual Studio 2012 and Entity Framework 6.

1. Open Visual Studio 2012 and create a console project.

Go to PROJECT menu of visual studio -> {project name} properties - and make sure that the project's target framework is .NET Framework 4.5, as shown below.

2. Now, add Entity Data Model by right clicking on the project in the solution explorer -> Add -> click New Item and select ADO.NET Entity Data Model from popup, Give the new item the name 'School' and click Add button.

3. Entity Data Model Wizard in VS2012 opens with four options to select from: EF Designer from database for database first approach, Empty EF Designer model for model first approach, Empty Code First model and Code First from database for Code-First approach. We will focus on the database-first approach in the basic tutorials so select EF Designer from database option and clickNext.

4. You can choose from your existing DB Connections or create a new connection by clicking on the 'New Connection' button. We will use the existing DB connection to the SchoolDB Database. This will also add a connection string to your app.config file with the default suffix with DB name. You can change this if you want. Click 'Next' after you set up your DB connection.

5. In this step, you need to choose the version of Entity Framework. We will use Entity Framework 6.0 in the basic tutorials so select Entity Framework 6.0 and click Next.

Note: If you have already installed the latest version of Entity Framework using NuGet manager as shown in the Setup Environment section then this step of the wizard will no longer appear since you have already installed Entity Framework.

6. This step will display all the Tables, Views and Stored Procedures (SP) in the database. Select the Tables, Views and SPs you want, keep the default checkboxes selected and click Finish. You can change Model Namespace if you want.

Note:

Pluralize or singularize generated object names checkbox singularizes an entityset name, if the table name in the database is plural. For example, if SchoolDB has Students table name then entityset would be singular Student. Similarly, relationships between the models will be pluralized if the table has one-to-many or many-to-many relationship with other tables. For example, Student has many-to-many relationship with Course table so Student entity set will have plural property name 'Courses' for the collection of courses.

The second checkbox, Include foreign key columns in the model, includes foreign key property explicitly to represent the foreign key. For example, Student table has one-to-many relationship with Standard table. So every student is associated with only one standard. To represent this in the model, Student entityset includes StandardId property with Standard navigation property. If this checkbox is unchecked then it will only include the Standard property, but not the StandardId in the Student entityset.

The third checkbox, Import selected stored procedures and functions into entity model, automatically creates Function Imports for the stored procedures and functions. You don't need to manually import this, as was necessary prior to Entity Framework 5.0.

7. After clicking on 'Finish', a School.edmx file will be added into your project.

Open EDM designer by double clicking on School.edmx. This displays all the entities for selected tables and the relationships between them as shown below:

EDM also adds a connection string in the config file as shown below.

<?xml version="1.0"?>
<configuration>
  <configSections>
    <!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
    <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/>
  </configSections>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
  </startup>
  <entityFramework>
    <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework"/>
    <providers>
      <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer"/>
    </providers>
  </entityFramework>
  <connectionStrings>
    <add name="SchoolDBEntities" connectionString="metadata=res://*/SchoolDB.csdl|res://*/SchoolDB.ssdl|res://*/SchoolDB.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=.\sqlexpress;initial catalog=SchoolDB;integrated security=True;multipleactiveresultsets=True;application name=EntityFramework&quot;" providerName="System.Data.EntityClient"/>
  </connectionStrings>
</configuration>

 

In this way, you can create a simple EDM from your existing database.

Now, let's examine all the building blocks of generated EDM (School.edmx) as shown in the above figure.

Entity-Table Mapping:

Each entity in EDM is mapped with the database table. You can check the entity-table mapping by right clicking on any entity in the EDM designer -> select Table Mapping. Also, if you change any property name of the entity from designer then the table mapping would reflect that change automatically.

Context & Entity Classes:

Every Entity Data Model generates one context class and entity class for each DB table included in the EDM. Expand School.edmx and see two important files, {EDM Name}.Context.tt and {EDM Name}.tt:

School.Context.tt: This T4 template file generates a context class whenever you change Entity Data Model (.edmx file). You can see the context class file by expanding School.Context.tt. The context class resides in {EDM Name}.context.cs file. The default context class name is {DB Name} + Entities. For example, the context class name for SchoolDB is SchoolDBEntities, then the context class is derived from DBContext class in Entity Framework. (Prior to EF 5.0 it had been derived from ObjectContext.)

School.tt: School.tt is a T4 template file that generates entity classes for each DB table. Entity classes are POCO (Plain Old CLR Object) classes. The following code snippet shows the Student entity.

public partial class Student
{
    public Student()
    {
        this.Courses = new HashSet<Course>();
    }
    
    public int StudentID { get; set; }
    public string StudentName { get; set; }
    public Nullable<int> StandardId { get; set; }
    public byte[] RowVersion { get; set; }
    
    public virtual Standard Standard { get; set; }
    public virtual StudentAddress StudentAddress { get; set; }
    public virtual ICollection<Course> Courses { get; set; }
}

 

EDM Designer: EDM designer represents your conceptual model. It consists of Entities, and associations & multiplicity between the entities. Initially, it will look exactly like your database table structure but you can add, merge or remove columns, which are not required by your application from this designer. You can even add a new object in this model, which can have columns from different database tables from context menu, as shown in the figure above. Remember, whatever changes done here should be mapped with the storage model. So you have to be careful, while making any changes in the designer.

You can open this EDM designer in XML view where you can see all the three parts of the EDM - Conceptual schema (CSDL), Storage schema (SSDL) and mapping schema (MSL), together in XML view.

Right click on School.edmx -> click 'Open with..', this will open a popup window.

Select 'XML (text) Editor' in the popup window.

Visual Studio cannot display the model in Design view and in XML format at the same time, so you will see a message asking whether it’s OK to close the Design view of the model. Click Yes. This will open the XML format view. You can see the following XML view by toggling all outlining as shown below.

You can see SSDL content, CSDL content and C-S mapping content here. If you expand SSDL and CSDL, each one has some common XML node under each schema node. You don't need to edit the xml data because this can be accomplished easier in the Model Browser.

Learn about Model Browser in the next section.