Creating MVC Applications Using Entity Framework Code First Approach

Jitan Gupta

12 Comments

Join the conversation! Your thoughts help the community grow.

Arjun Dhilod8y ago
Jitan Bhai Nice keep it up
Mister Meeseeks8y ago
I get lost right about the time it talks about the Global.aspx file editing. I can't find the Global.aspx file - I only see a Global.asax file? I keep getting errors that the "FilterConfig", "BundleConfig" and "BundleTable" do not exist in the current context as well. Thank you!
Trends Technology8y ago
Https://youtu.be/tjDO_5jppSM
Fatemeh Fallahi8y ago
Thank you sir for this article
Srini vasan9y ago
Kindly assist me.I need your help to modify my existing hosted portal in aws mvc entity .net based. give ur number or mail me [email protected]
Manav Pandya9y ago
Code first is not mostly helpful bcoz every time database is re-generated
- Jitan Gupta9y ago
  1>CreateDatabaseIfNotExists 2>DropCreateDatabaseIfModelChanges 3>DropCreateDatabaseAlways Based on your requirement you can choose whichever you want. Code first is basically used in the development phase.
Manav Pandya9y ago
But which approach do we need in real life application
Manav Pandya9y ago
Nice article posted sir @jitan ....
kalu singh rao9y ago
Good Job. Keep it. Thanks for sharing
Jaco Zwarts9y ago
Thank you for sharing this Jitan
Amatya Agyey9y ago
Nice article man... Keep it up

Entity Framework is a relational mapper framework. It is an enhancement of ADO.NET that gives developers an automated mechanism for accessing and storing the data in the database.

Types

Code First
Model First
Database First

Code First

It was introduced in EF 4.1. It is mainly used for domain driven design, i.e., we write our business requirement as models and based on that, EF creates the database.

For creating a database, there are three methods offered by code first approach.

CreateDatabaseIfNotExists
As the name suggests, if your database does not exist, then it creates that for you.
DropCreateDatabaseIfModelChanges
Suppose, we have our business logic already and a database is also created on that basis, but we need to change our business models, then we can use this class.
DropCreateDatabaseAlways
It drops and re-creates the database every time it runs. This approach is helpful for testing purposes. Every time it runs, it seeds some sample data to the database and based on that, we can test our application.

At the time when we extend DbContext to our context class by default, CreateDatabaseIfNotExist method initializes.

If we want to change the initialization process, we can create an initializer class and extend it by encapsulating the same class which extends DbContext class.

Let's see all this with an example for better understanding.

Now, name your project.

Click OK and select Empty template.

This will create a blank MVC 5 project.

Now, start your Package Manager Console by going into Tools -> NuGet Package Manager -> Package Manager Console.

In Package Manger Console, type Install-Package EntityFramework.

This will install Entity Framework's latest stable version.

Now, create your Student Model in Models folder.

using System;
namespace test.Models
{
public class Student
{
public int Id { get; set; }
public string Name { get; set; }
public DateTime DoB { get; set; }
public Gender Gender { get; set; }
public int Flag { get; set; }
}
public enum Gender
{
Male, Female, Other
}
}

Then, build your solution and add a new folder called Context.

In Context folder, add a class called DatabaseContext and extend DbContext class. This is the main class which implements all Entity Framework functionality.

In Database Context class, write the following code.

using System.Data.Entity;
using System.Data.Entity.ModelConfiguration.Conventions;
using test.Models;
namespace test.Context
{
public class DatabaseContext : DbContext
{
public DatabaseContext() : base("StudentDatabase")
{ }
public DbSet<Student> Students { get; set; }
protected override void OnModelCreating(DbModelBuilder modelBuilder)
{
modelBuilder.Conventions.Remove<PluralizingTableNameConvention>();
}
}
}

The parameter accepted by the constructor is our database name. If we are not making any constructor in DatabaseContext class, then the database name will be same as the class name that extends the DbContext class ( DatabaseContext in this case).

This will create a property for Student Entity set.

Note - This code will create a pluralized table name in database and if we want to remove that convention, then we have to override OnModelCreating method in DatabaseContext Class, as shown below.

For seeding the data, when a database is being created, we can override the seed method in initializer class.

The databaseInitializer class inherits (red bordered) one of the three classes offered by entity framework to create database.

Now, register your DatabaseInitializer in Application_Start() method of Global.aspx file.

using test.Context;
using System.Data.Entity;
namespace test
{
public class Global : System.Web.HttpApplication
{
protected void Application_Start(object sender, EventArgs e)
{
AreaRegistration.RegisterAllAreas();
RouteConfig.RegisterRoutes(RouteTable.Routes);
FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
BundleConfig.RegisterBundles(BundleTable.Bundles);
Database.SetInitializer(new DatabaseInitializer());
}
}
}

Add Connection string in web.config file.

Now, build your solution.

Once the solution is built successfully, go to Controller folder and add Controller with Views, using Entity framework.

Name the Controller as StudentController.

Once you add this Controller, Scaffold templates will create all read-write action with views, using Entity Framework.

Now, go to RouteConfig.cs file to change the default route from Home to Student in App_Start folder and run the application. It will run successfully.

Note - If you want to attach database.mdf file, then add AttachDbFilename=|DataDirectory|\<databaseName>; to your connection string in web.config file.