Create a Movie Database Application in 15 Minutes with ASP.NET MVC (C#)
Stephen Walther builds an entire database-driven ASP.NET MVC application from start to finish. This tutorial is a great introduction for people who are new to the ASP.NET MVC Framework and who want to get a sense of the process of building an ASP.NET MVC application.
The purpose of this tutorial is to give you a sense of “what it is like” to build an ASP.NET MVC application. In this tutorial, I blast through building an entire ASP.NET MVC application from start to finish. I show you how to build a simple database-driven application that illustrates how you can list, create, and edit database records.
To simplify the process of building our application, we’ll take advantage of the scaffolding features of Visual Studio 2008. We’ll let Visual Studio generate the initial code and content for our controllers, models, and views.
If you have worked with Active Server Pages or ASP.NET, then you should find ASP.NET MVC very familiar. ASP.NET MVC views are very much like the pages in an Active Server Pages application. And, just like a traditional ASP.NET Web Forms application, ASP.NET MVC provides you with full access to the rich set of languages and classes provided by the .NET framework.
My hope is that this tutorial will give you a sense of how the experience of building an ASP.NET MVC application is both similar and different than the experience of building an Active Server Pages or ASP.NET Web Forms application.
Overview of the Movie Database Application
Because our goal is to keep things simple, we’ll build a very simple Movie Database application. Our simple Movie Database application will allow us to do three things:
- List a set of movie database records
- Create a new movie database record
- Edit an existing movie database record
Again, because we want to keep things simple, we’ll take advantage of the minimum number of features of the ASP.NET MVC framework needed to build our application. For example, we won’t be taking advantage of Test-Driven Development.
In order to create our application, we need to complete each of the following steps:
- Create the ASP.NET MVC Web Application Project
- Create the database
- Create the database model
- Create the ASP.NET MVC controller
- Create the ASP.NET MVC views
Preliminaries
You’ll need either Visual Studio 2008 or Visual Web Developer 2008 Express to build an ASP.NET MVC application. You also need to download the ASP.NET MVC framework.
If you don’t own Visual Studio 2008, then you can download a 90 day trial version of Visual Studio 2008 from this website:
https://msdn.microsoft.com/en-us/vs2008/products/cc268305.aspx
Alternatively, you can create ASP.NET MVC applications with Visual Web Developer Express 2008. If you decide to use Visual Web Developer Express then you must have Service Pack 1 installed. You can download Visual Web Developer 2008 Express with Service Pack 1 from this website:
After you install either Visual Studio 2008 or Visual Web Developer 2008, you need to install the ASP.NET MVC framework. You can download the ASP.NET MVC framework from the following website:
[!NOTE]
Instead of downloading the ASP.NET framework and the ASP.NET MVC framework individually, you can take advantage of the Web Platform Installer. The Web Platform Installer is an application that enables you to easily manage the installed applications are your computer:
Creating an ASP.NET MVC Web Application Project
Let’s start by creating a new ASP.NET MVC Web Application project in Visual Studio 2008. Select the menu option File, New Project and you will see the New Project dialog box in Figure 1. Select C# as the programming language and select the ASP.NET MVC Web Application project template. Give your project the name MovieApp and click the OK button.
Figure 01: The New Project dialog box (Click to view full-size image)
Make sure that you select .NET Framework 3.5 from the dropdown list at the top of the New Project dialog or the ASP.NET MVC Web Application project template won’t appear.
Whenever you create a new MVC Web Application project, Visual Studio prompts you to create a separate unit test project. The dialog in Figure 2 appears. Because we won’t be creating tests in this tutorial because of time constraints (and, yes, we should feel a little guilty about this) select the No option and click the OK button.
[!NOTE]
Visual Web Developer does not support test projects.
Figure 02: The Create Unit Test Project dialog (Click to view full-size image)
An ASP.NET MVC application has a standard set of folders: a Models, Views, and Controllers folder. You can see this standard set of folders in the Solution Explorer window. We’ll need to add files to each of the Models, Views, and Controllers folders in order to build our Movie Database application.
When you create a new MVC application with Visual Studio, you get a sample application. Because we want to start from scratch, we need to delete the content for this sample application. You need to delete the following file and the following folder:
- Controllers.cs
- Views
Creating the Database
We need to create a database to hold our movie database records. Luckily, Visual Studio includes a free database named SQL Server Express. Follow these steps to create the database:
- Right-click the App_Data folder in the Solution Explorer window and select the menu option Add, New Item.
- Select the Data category and select the SQL Server Database template (see Figure 3).
- Name your new database MoviesDB.mdf and click the Add button.
After you create your database, you can connect to the database by double-clicking the MoviesDB.mdf file located in the App_Data folder. Double-clicking the MoviesDB.mdf file opens the Server Explorer window.
[!NOTE]
The Server Explorer window is named the Database Explorer window in the case of Visual Web Developer.
Figure 03: Creating a Microsoft SQL Server Database (Click to view full-size image)
Next, we need to create a new database table. From within the Sever Explorer window, right-click the Tables folder and select the menu option Add New Table. Selecting this menu option opens the database table designer. Create the following database columns:
| Column Name | Data Type | Allow Nulls |
|---|---|---|
| Id | Int | False |
| Title | Nvarchar(100) | False |
| Director | Nvarchar(100) | False |
| DateReleased | DateTime | False |
The first column, the Id column, has two special properties. First, you need to mark the Id column as the primary key column. After selecting the Id column, click the Set Primary Key button (it is the icon that looks like a key). Second, you need to mark the Id column as an Identity column. In the Column Properties window, scroll down to the Identity Specification section and expand it. Change the Is Identity property to the value Yes. When you are finished, the table should look like Figure 4.
Figure 04: The Movies database table (Click to view full-size image)
The final step is to save the new table. Click the Save button (the icon of the floppy) and give the new table the name Movies.
After you finish creating the table, add some movie records to the table. Right-click the Movies table in the Server Explorer window and select the menu option Show Table Data. Enter a list of your favorite movies (see Figure 5).
Figure 05: Entering movie records (Click to view full-size image)
Creating the Model
We next need to create a set of classes to represent our database. We need to create a database model. We’ll take advantage of the Microsoft Entity Framework to generate the classes for our database model automatically.
[!NOTE]
The ASP.NET MVC framework is not tied to the Microsoft Entity Framework. You can create your database model classes by taking advantage of a variety of Object Relational Mapping (OR/M) tools including LINQ to SQL, Subsonic, and NHibernate.
Follow these steps to launch the Entity Data Model Wizard:
- Right-click the Models folder in the Solution Explorer window and the select the menu option Add, New Item.
- Select the Data category and select the ADO.NET Entity Data Model template.
- Give your data model the name MoviesDBModel.edmx and click the Add button.
After you click the Add button, the Entity Data Model Wizard appears (see Figure 6). Follow these steps to complete the wizard:
- In the Choose Model Contents step, select the Generate from database option.
- In the Choose Your Data Connection step, use the MoviesDB.mdf data connection and the name MoviesDBEntities for the connection settings. Click the Next button.
- In the Choose Your Database Objects step, expand the Tables node, select the Movies table. Enter the namespace MovieApp.Models and click the Finish button.
Figure 06: Generating a database model with the Entity Data Model Wizard (Click to view full-size image)
After you complete the Entity Data Model Wizard, the Entity Data Model Designer opens. The Designer should display the Movies database table (see Figure 7).
Figure 07: The Entity Data Model Designer (Click to view full-size image)
We need to make one change before we continue. The Entity Data Wizard generates a model class named Movies that represents the Movies database table. Because we’ll use the Movies class to represent a particular movie, we need to modify the name of the class to be Movie instead of Movies (singular rather than plural).
Double-click the name of the class on the designer surface and change the name of the class from Movies to Movie. After making this change, click the Save button (the icon of the floppy disk) to generate the Movie class.
Creating the ASP.NET MVC Controller
The next step is to create the ASP.NET MVC controller. A controller is responsible for controlling how a user interacts with an ASP.NET MVC application.
Follow these steps:
- In the Solution Explorer window, right-click the Controllers folder and select the menu option Add, Controller.
- In the Add Controller dialog, enter the name HomeController and check the checkbox labeled Add action methods for Create, Update, and Details scenarios (see Figure 8).
- Click the Add button to add the new controller to your project.
After you complete these steps, the controller in Listing 1 is created. Notice that it contains methods named Index, Details, Create, and Edit. In the following sections, we’ll add the necessary code to get these methods to work.
Figure 08: Adding a new ASP.NET MVC Controller (Click to view full-size image)
Listing 1 – Controllers.cs
[!code-csharpMain]
1: using System;
2:
3: using System.Collections.Generic;
4:
5: using System.Linq;
6:
7: using System.Web;
8:
9: using System.Web.Mvc;
10:
11: using System.Web.Mvc.Ajax;
12:
13: namespace MovieApp.Controllers
14:
15: {
16:
17: public class HomeController : Controller
18:
19: {
20:
21: //
22:
23: // GET: /Home/
24:
25: public ActionResult Index()
26:
27: {
28:
29: return View();
30:
31: }
32:
33: //
34:
35: // GET: /Home/Details/5
36:
37: public ActionResult Details(int id)
38:
39: {
40:
41: return View();
42:
43: }
44:
45: //
46:
47: // GET: /Home/Create
48:
49: public ActionResult Create()
50:
51: {
52:
53: return View();
54:
55: }
56:
57: //
58:
59: // POST: /Home/Create
60:
61: [AcceptVerbs(HttpVerbs.Post)]
62:
63: public ActionResult Create(FormCollection collection)
64:
65: {
66:
67: try
68:
69: {
70:
71: // TODO: Add insert logic here
72:
73: return RedirectToAction("Index");
74:
75: }
76:
77: catch
78:
79: {
80:
81: return View();
82:
83: }
84:
85: }
86:
87: //
88:
89: // GET: /Home/Edit/5
90:
91: public ActionResult Edit(int id)
92:
93: {
94:
95: return View();
96:
97: }
98:
99: //
100:
101: // POST: /Home/Edit/5
102:
103: [AcceptVerbs(HttpVerbs.Post)]
104:
105: public ActionResult Edit(int id, FormCollection collection)
106:
107: {
108:
109: try
110:
111: {
112:
113: // TODO: Add update logic here
114:
115: return RedirectToAction("Index");
116:
117: }
118:
119: catch
120:
121: {
122:
123: return View();
124:
125: }
126:
127: }
128:
129: }
130:
131: }
Listing Database Records
The Index() method of the Home controller is the default method for an ASP.NET MVC application. When you run an ASP.NET MVC application, the Index() method is the first controller method that is called.
We’ll use the Index() method to display the list of records from the Movies database table. We’ll take advantage of the database model classes that we created earlier to retrieve the movie database records with the Index() method.
I’ve modified the HomeController class in Listing 2 so that it contains a new private field named _db. The MoviesDBEntities class represents our database model and we’ll use this class to communicate with our database.
I’ve also modified the Index() method in Listing 2. The Index() method uses the MoviesDBEntities class to retrieve all of the movie records from the Movies database table. The expression _db.MovieSet.ToList() returns a list of all of the movie records from the Movies database table.
The list of movies is passed to the view. Anything that gets passed to the View() method gets passed to the view as view data.
Listing 2 – Controllers/HomeController.cs (modified Index method)
[!code-csharpMain]
1: using System.Linq;
2:
3: using System.Web.Mvc;
4:
5: using MovieApp.Models;
6:
7: namespace MovieApp.Controllers
8:
9: {
10:
11: public class HomeController : Controller
12:
13: {
14:
15: private MoviesDBEntities _db = new MoviesDBEntities();
16:
17: public ActionResult Index()
18:
19: {
20:
21: return View(_db.MovieSet.ToList());
22:
23: }
24:
25: }
26:
27: }
The Index() method returns a view named Index. We need to create this view to display the list of movie database records. Follow these steps:
You should build your project (select the menu option Build, Build Solution) before opening the Add View dialog or no classes will appear in the View data class dropdown list.
- Right-click the Index() method in the code editor and select the menu option Add View (see Figure 9).
- In the Add View dialog, verify that the checkbox labeled Create a strongly-typed view is checked.
- From the View content dropdown list, select the value List.
- From the View data class dropdown list, select the value MovieApp.Models.Movie.
- Click the Add button to create the new view (see Figure 10).
After you complete these steps, a new view named Index.aspx is added to the Viewsfolder. The contents of the Index view are included in Listing 3.
Figure 09: Adding a view from a controller action (Click to view full-size image)
Figure 10: Creating a new view with the Add View dialog (Click to view full-size image)
Listing 3 – Views.aspx
[!code-aspxMain]
1: <%@ Page Title="" Language="C#" MasterPageFile="~/Views/Shared/Site.Master" Inherits="System.Web.Mvc.ViewPage<IEnumerable<MovieApp.Models.Movie>>" %>
2:
3: <asp:Content ID="Content1" ContentPlaceHolderID="TitleContent" runat="server">
4:
5: Index
6:
7: </asp:Content>
8:
9: <asp:Content ID="Content2" ContentPlaceHolderID="MainContent" runat="server">
10:
11: <h2>Index</h2>
12:
13: <table>
14:
15: <tr>
16:
17: <th></th>
18:
19: <th>
20:
21: Id
22:
23: </th>
24:
25: <th>
26:
27: Title
28:
29: </th>
30:
31: <th>
32:
33: Director
34:
35: </th>
36:
37: <th>
38:
39: DateReleased
40:
41: </th>
42:
43: </tr>
44:
45: <% foreach (var item in Model) { %>
46:
47: <tr>
48:
49: <td>
50:
51: <%= Html.ActionLink("Edit", "Edit", new { id=item.Id }) %> |
52:
53: <%= Html.ActionLink("Details", "Details", new { id=item.Id })%>
54:
55: </td>
56:
57: <td>
58:
59: <%= Html.Encode(item.Id) %>
60:
61: </td>
62:
63: <td>
64:
65: <%= Html.Encode(item.Title) %>
66:
67: </td>
68:
69: <td>
70:
71: <%= Html.Encode(item.Director) %>
72:
73: </td>
74:
75: <td>
76:
77: <%= Html.Encode(String.Format("{0:g}", item.DateReleased)) %>
78:
79: </td>
80:
81: </tr>
82:
83: <% } %>
84:
85: </table>
86:
87: <p>
88:
89: <%= Html.ActionLink("Create New", "Create") %>
90:
91: </p>
92:
93: </asp:Content>
The Index view displays all of the movie records from the Movies database table within an HTML table. The view contains a foreach loop that iterates through each movie represented by the ViewData.Model property. If you run your application by hitting the F5 key, then you’ll see the web page in Figure 11.
Figure 11: The Index view (Click to view full-size image)
Creating New Database Records
The Index view that we created in the previous section includes a link for creating new database records. Let’s go ahead and implement the logic and create the view necessary for creating new movie database records.
The Home controller contains two methods named Create(). The first Create() method has no parameters. This overload of the Create() method is used to display the HTML form for creating a new movie database record.
The second Create() method has a FormCollection parameter. This overload of the Create() method is called when the HTML form for creating a new movie is posted to the server. Notice that this second Create() method has an AcceptVerbs attribute that prevents the method from being called unless an HTTP POST operation is performed.
This second Create() method has been modified in the updated HomeController class in Listing 4. The new version of the Create() method accepts a Movie parameter and contains the logic for inserting a new movie into the Movies database table.
[!NOTE]
Notice the Bind attribute. Because we don’t want to update the Movie Id property from HTML form, we need to explicitly exclude this property.
Listing 4 – Controllers.cs (modified Create method)
[!code-csharpMain]
1: //
2:
3: // GET: /Home/Create
4:
5: public ActionResult Create()
6:
7: {
8:
9: return View();
10:
11: }
12:
13: //
14:
15: // POST: /Home/Create
16:
17: [AcceptVerbs(HttpVerbs.Post)]
18:
19: public ActionResult Create([Bind(Exclude="Id")] Movie movieToCreate)
20:
21: {
22:
23: if (!ModelState.IsValid)
24:
25: return View();
26:
27: _db.AddToMovieSet(movieToCreate);
28:
29: _db.SaveChanges();
30:
31: return RedirectToAction("Index");
32:
33: }
Visual Studio makes it easy to create the form for creating a new movie database record (see Figure 12). Follow these steps:
- Right-click the Create() method in the code editor and select the menu option Add View.
- Verify that the checkbox labeled Create a strongly-typed view is checked.
- From the View content dropdown list, select the value Create.
- From the View data class dropdown list, select the value MovieApp.Models.Movie.
- Click the Add button to create the new view.
Figure 12: Adding the Create view (Click to view full-size image)
Visual Studio generates the view in Listing 5 automatically. This view contains an HTML form that includes fields that correspond to each of the properties of the Movie class.
Listing 5 – Views.aspx
[!code-aspxMain]
1: <%@ Page Title="" Language="C#" MasterPageFile="~/Views/Shared/Site.Master" Inherits="System.Web.Mvc.ViewPage<MovieApp.Models.Movie>" %>
2:
3: <asp:Content ID="Content1" ContentPlaceHolderID="TitleContent" runat="server">
4:
5: Create
6:
7: </asp:Content>
8:
9: <asp:Content ID="Content2" ContentPlaceHolderID="MainContent" runat="server">
10:
11: <h2>Create</h2>
12:
13: <%= Html.ValidationSummary("Create was unsuccessful. Please correct the errors and try again.") %>
14:
15: <% using (Html.BeginForm()) {%>
16:
17: <fieldset>
18:
19: <legend>Fields</legend>
20:
21: <p>
22:
23: <label for="Id">Id:</label>
24:
25: <%= Html.TextBox("Id") %>
26:
27: <%= Html.ValidationMessage("Id", "*") %>
28:
29: </p>
30:
31: <p>
32:
33: <label for="Title">Title:</label>
34:
35: <%= Html.TextBox("Title") %>
36:
37: <%= Html.ValidationMessage("Title", "*") %>
38:
39: </p>
40:
41: <p>
42:
43: <label for="Director">Director:</label>
44:
45: <%= Html.TextBox("Director") %>
46:
47: <%= Html.ValidationMessage("Director", "*") %>
48:
49: </p>
50:
51: <p>
52:
53: <label for="DateReleased">DateReleased:</label>
54:
55: <%= Html.TextBox("DateReleased") %>
56:
57: <%= Html.ValidationMessage("DateReleased", "*") %>
58:
59: </p>
60:
61: <p>
62:
63: <input type="submit" value="Create" />
64:
65: </p>
66:
67: </fieldset>
68:
69: <% } %>
70:
71: <div>
72:
73: <%=Html.ActionLink("Back to List", "Index") %>
74:
75: </div>
76:
77: </asp:Content>
[!NOTE]
The HTML form generated by the Add View dialog generates an Id form field. Because the Id column is an Identity column, we don’t need this form field and you can safely remove it.
After you add the Create view, you can add new Movie records to the database. Run your application by pressing the F5 key and click the Create New link to see the form in Figure 13. If you complete and submit the form, a new movie database record is created.
Notice that you get form validation automatically. If you neglect to enter a release date for a movie, or you enter an invalid release date, then the form is redisplayed and the release date field is highlighted.
Figure 13: Creating a new movie database record (Click to view full-size image)
Editing Existing Database Records
In the previous sections, we discussed how you can list and create new database records. In this final section, we discuss how you can edit existing database records.
First, we need to generate the Edit form. This step is easy since Visual Studio will generate the Edit form for us automatically. Open the HomeController.cs class in the Visual Studio code editor and follow these steps:
- Right-click the Edit() method in the code editor and select the menu option Add View (see Figure 14).
- Check the checkbox labeled Create a strongly-typed view.
- From the View content dropdown list, select the value Edit.
- From the View data class dropdown list, select the value MovieApp.Models.Movie.
- Click the Add button to create the new view.
Completing these steps adds a new view named Edit.aspx to the Viewsfolder. This view contains an HTML form for editing a movie record.
Figure 14: Adding the Edit view (Click to view full-size image)
[!NOTE]
The Edit view contains an HTML form field that corresponds to the Movie Id property. Because you don’t want people editing the value of the Id property, you should remove this form field.
Finally, we need to modify the Home controller so that it supports editing a database record. The updated HomeController class is contained in Listing 6.
Listing 6 – Controllers.cs (Edit methods)
[!code-csharpMain]
1: //
2:
3: // GET: /Home/Edit/5
4:
5: public ActionResult Edit(int id)
6:
7: {
8:
9: var movieToEdit = (from m in _db.MovieSet
10:
11: where m.Id == id
12:
13: select m).First();
14:
15: return View(movieToEdit);
16:
17: }
18:
19: //
20:
21: // POST: /Home/Edit/5
22:
23: [AcceptVerbs(HttpVerbs.Post)]
24:
25: public ActionResult Edit(Movie movieToEdit)
26:
27: {
28:
29: var originalMovie = (from m in _db.MovieSet
30:
31: where m.Id == movieToEdit.Id
32:
33: select m).First();
34:
35: if (!ModelState.IsValid)
36:
37: return View(originalMovie);
38:
39: _db.ApplyPropertyChanges(originalMovie.EntityKey.EntitySetName, movieToEdit);
40:
41: _db.SaveChanges();
42:
43: return RedirectToAction("Index");
44:
45: }
In Listing 6, I’ve added additional logic to both overloads of the Edit() method. The first Edit() method returns the movie database record that corresponds to the Id parameter passed to the method. The second overload performs the updates to a movie record in the database.
Notice that you must retrieve the original movie, and then call ApplyPropertyChanges(), to update the existing movie in the database.
Summary
The purpose of this tutorial was to give you a sense of the experience of building an ASP.NET MVC application. I hope that you discovered that building an ASP.NET MVC web application is very similar to the experience of building an Active Server Pages or ASP.NET application.
In this tutorial, we examined only the most basic features of the ASP.NET MVC framework. In future tutorials, we dive deeper into topics such as controllers, controller actions, views, view data, and HTML helpers.
)
|
|