|Read more about this book|
(For more resources on .NET, see here.)
How to create a master page
In this recipe, we will take a look at how to create a master page and associate it with our view. Part of creating a master page is defining placeholders for use in the view. We will then see how to utilize the content placeholders that we defined in the master page.
How to do it…
- Start by creating a new ASP.NET MVC application.
- Then add a new master page to your solution called Custom.Master. Place it in the Views/Shared directory.
- Notice that there is a placeholder already placed in the middle of our page. Let’s wrap that placeholder with a table. We will put a column to the left and the right of the existing placeholder. Then we will rename the placeholder to MainContent.
- Next, we will copy the placeholder into the first and the third columns.
- Next, we need to add a new action to the HomeController.cs file, from which we will create a new view. Do this by opening the HomeController.cs file, then add a new action named CustomMasterDemo.
public ActionResult CustomMasterDemo()
- Then right-click on the CustomerMasterDemo and choose AddView, and select the new Custom.Master page that we created. Next, you need to change the ContentPlaceHolderID box to show the center placeholder name ContentPlaceHolder2. Then hit Add and you should see a new view with four placeholders.
<asp:Content ID="Content1" ContentPlaceHolderID="MainContent"
<h2>Custom Master Demo</h2>
<asp:Content ID="Content2" ContentPlaceHolderID="head"
<meta name="description" content="Here are some keywords for our
<div style="width:200px;height:200px;border:1px solid #ff0000;">
<div style="width:200px;height:200px;border:1px solid #000000;">
Here is a blurb of text on the right!
- You should now see a page similar to this:
How it works…
This particular feature is a server-side carry over from web forms. It works just as it always has. Before being sent down to the client, the view is merged into the master file and processed according to the matching placeholder IDs.
Determining the master page in the ActionResult
In the previous recipe, we took a look at how to build a master page. In this recipe, we are going to take a look at how to control what master page to use programmatically. There are all sorts of reasons for using different master pages. For example, you might want to use different master pages based on the time of day, if a user is logged in or not, for different areas of your site (blog, shopping, forum, and so on).
How to do it…
- We will get started by first creating a new MVC web application.
- Next, we need to create a second master page. We can do this quickly by making a copy of the default master page that is provided. Name it Site2.Master.
- Next, we need to make sure we can tell these two master pages apart. The easiest way to do this is to change the contents of the H1 tag to say Master 1 and Master 2 in each of the master pages.
- Now we can take a look at the HomeController. We will check if we are in an even or odd second and based on that we can return an even or odd master page. We do this by specifying the master page name that we want to use when we return the view.
public ActionResult Index()
ViewData["Message"] = "Welcome to ASP.NET MVC!";
string masterName = "";
if (DateTime.Now.Second % 2 == 0)
masterName = "Site2";
masterName = "Site";
return View("Index", masterName);
- Now you can run the application. Refreshing the home page should alternate between the two master pages now and then. (Remember that this is based on the second and is now just a pure alternating page scheme.)
How it works…
This method of controlling which master page is used by the view is built into the MVC framework and is the easiest way of performing this type of control. However, having to dictate this type of logic in every single action would create quite a bit of fluff code in our controller. This option might be appropriate for certain needs though!