o_19mgorv9t13a3ko71fev19l81mqa.pdf

new { controller = "Home", action = "Index" });
}
}
}
routes.MapRoute("", "Public/{controller}/{action}",
new { controller = "Home", action = "Index" });
This new pattern will match only URLs that contain three segments, the first of which must be Public. The other two
segments can contain any value, and will be used for the controller and action variables. If the last two segments are
omitted, then the default values will be used.
I can also create URL patterns that have segments containing both static and variable elements, such as the one shown in Listing
15-12.
Listing 15-12. A URL Pattern with a Mixed Segment in the RouteConfig.cs File
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using System.Web.Routing;
namespace UrlsAndRoutes {
public class RouteConfig {
public static void RegisterRoutes(RouteCollection routes) {
routes.MapRoute("", "X{controller}/{action}");
routes.MapRoute("MyRoute", "{controller}/{action}",
new { controller = "Home", action = "Index" });
}
}
}
routes.MapRoute("", "Public/{controller}/{action}",
new { controller = "Home", action = "Index" });
The pattern in this route matches any two-segment URL where the first segment starts with the letter X. The value for
controller is taken from the first segment, excluding the X. The action value is taken from the second segment. You
can see the effect of this route if you start the application and navigate to /XHome/Index, the result of which is illustrated by
Figure 15-6.
Figure 15-6. Mixing static and variable elements in a single segment
ROUTE ORDERING
373