Blog

ASP.NET
MVC: Guidance Videos Samples Forum Books Open Source

Older Versions - MVC 1 and 2 +

ASP.NET MVC Routing Overview (C#)
By Stephen Walther | August 19, 2008
135 of 165 people found this helpful
Like 18 Print

In this tutorial, Stephen Walther shows how the ASP.NET MVC framework maps browser requests to controller actions.

In this tutorial, you are introduced to an important feature of every ASP.NET MVC application called ASP.NET Routing. The ASP.NET
Routing module is responsible for mapping incoming browser requests to particular MVC controller actions. By the end of this tutorial, you
will understand how the standard route table maps requests to controller actions.

Using the Default Route Table

When you create a new ASP.NET MVC application, the application is already configured to use ASP.NET Routing. ASP.NET Routing is
setup in two places.

open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 First, ASP.NET Routing is enabled in your application's Web configuration file (Web.config file). There are four sections in the
configuration file that are relevant to routing: the system.web.httpModules section, the system.web.httpHandlers section, the
system.webserver.modules section, and the system.webserver.handlers section. Be careful not to delete these sections because without
these sections routing will no longer work.

Second, and more importantly, a route table is created in the application's Global.asax file. The Global.asax file is a special file that
contains event handlers for ASP.NET application lifecycle events. The route table is created during the Application Start event.

The file in Listing 1 contains the default Global.asax file for an ASP.NET MVC application.

Listing 1 - Global.asax.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using System.Web.Routing;

namespace MvcApplication1
{
// Note: For instructions on enabling IIS6 or IIS7 classic mode,
// visit http://go.microsoft.com/?LinkId=9394801

public class MvcApplication : System.Web.HttpApplication

{
public static void RegisterRoutes(RouteCollection routes)
{
routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

routes.MapRoute(
open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 "Default", // Route name
"{controller}/{action}/{id}", // URL with parameters
new { controller = "Home", action = "Index", id = "" } // Parameter defaults
);

protected void Application_Start()

{
RegisterRoutes(RouteTable.Routes);
}
}
}

When an MVC application first starts, the Application_Start() method is called. This method, in turn, calls the RegisterRoutes() method.
The RegisterRoutes() method creates the route table.

The default route table contains a single route (named Default). The Default route maps the first segment of a URL to a controller name,
the second segment of a URL to a controller action, and the third segment to a parameter named id.

Imagine that you enter the following URL into your web browser's address bar:

/Home/Index/3

The Default route maps this URL to the following parameters:

controller = Home

action = Index

open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 id = 3

When you request the URL /Home/Index/3, the following code is executed:

HomeController.Index(3)

The Default route includes defaults for all three parameters. If you don't supply a controller, then the controller parameter defaults to the
value Home. If you don't supply an action, the action parameter defaults to the value Index. Finally, if you don't supply an id, the id
parameter defaults to an empty string.

Let's look at a few examples of how the Default route maps URLs to controller actions. Imagine that you enter the following URL into your
browser address bar:

/Home

Because of the Default route parameter defaults, entering this URL will cause the Index() method of the HomeController class in Listing 2
to be called.

Listing 2 - HomeController.cs

using System.Web.Mvc;

namespace MvcApplication1.Controllers
{
[HandleError]
public class HomeController : Controller
{
public ActionResult Index(string id)
{
return View();
}
open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 }
}

In Listing 2, the HomeController class includes a method named Index() that accepts a single parameter named Id. The URL /Home
causes the Index() method to be called with an empty string as the value of the Id parameter.

Because of the way that the MVC framework invokes controller actions, the URL /Home also matches the Index() method of the
HomeController class in Listing 3.

Listing 3 - HomeController.cs (Index action with no parameter)

using System.Web.Mvc;

namespace MvcApplication1.Controllers
{
[HandleError]
public class HomeController : Controller
{
public ActionResult Index()
{
return View();
}
}
}

The Index() method in Listing 3 does not accept any parameters. The URL /Home will cause this Index() method to be called. The URL
/Home/Index/3 also invokes this method (the Id is ignored).

The URL /Home also matches the Index() method of the HomeController class in Listing 4.
open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 Listing 4 - HomeController.cs (Index action with nullable parameter)

using System.Web.Mvc;

namespace MvcApplication1.Controllers
{
[HandleError]
public class HomeController : Controller
{
public ActionResult Index(int? id)
{
return View();
}
}
}

In Listing 4, the Index() method has one Integer parameter. Because the parameter is a nullable parameter (can have the value Null), the
Index() can be called without raising an error.

Finally, invoking the Index() method in Listing 5 with the URL /Home causes an exception since the Id parameter is not a nullable
parameter. If you attempt to invoke the Index() method then you get the error displayed in Figure 1.

Listing 5 - HomeController.cs (Index action with Id parameter)

using System.Web.Mvc;

namespace MvcApplication1.Controllers
{
[HandleError]
open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 public class HomeController : Controller
{
public ActionResult Index(int id)
{
return View();
}
}
}

Figure 01: Invoking a controller action that expects a parameter value (Click to view full-size image)

The URL /Home/Index/3, on the other hand, works just fine with the Index controller action in Listing 5. The request /Home/Index/3
causes the Index() method to be called with an Id parameter that has the value 3.

Summary
The goal of this tutorial was to provide you with a brief introduction to ASP.NET Routing. We examined the default route table that you get
with a new ASP.NET MVC application. You learned how the default route maps URLs to controller actions.

This article was originally created on August 19, 2008

Like 18

open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 Author Information

Stephen Walther – Stephen Walther has been involved with ASP.NET from the beginning. His training company,
AspWorkshops.com and superexperttraining.com, conducted the first training class on ASP.NET. He also lectures
regularly on ASP.NET and he is a Microsoft ASP.NET MVP.

You're Viewing → Next

ASP.NET MVC Routing Overview (C#) Understanding Action Filters (C#)

Comments (0)
You must be logged in to leave a comment.

This site is managed for Microsoft by Neudesic, LLC. | © 2015 Microsoft. All rights reserved.

Privacy Statement | Terms of Use | Contact Us | Advertise With Us | CMS by Umbraco | Hosted on Microsoft Azure

open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com
 Feedback on ASP.NET | File Bugs | Support Lifecycle

open in browser PRO version Are you a developer? Try out the HTML to PDF API pdfcrowd.com