Advanced ASP Routing tutorials and examples
One of major hurdles I seem to be having recently is getting my head around some of the more complex routing requirements for some MVC based applications I've been developing. I'm having problems finding the right set of tutorials to walk me through it to get a complete understanding.
What I'd like to find is a complete set of tutorials for everything routing from basic (controller/action/id) to advanced.
An example of what I'm calling advanced routing is things like:
/blog/year/month/day/title - would map to controller: blog and action: post and as parameters: year, month, day and title
/blog/title - would map to controller: blog and action: post and as parameters: title
/title - would map to controller: blog and action: post and as parameters: title
I could map each possible set to an explicit route in global using a database, but that seems like it's defeating the point of having the routing engine route to the correct place. I'd rather define the rule once.
Answer
I don't understand, why can't you just define each one of them as a separate route, using regular expression when needed. For example to differentiate between the /blog/year/month/day/title and /blog/title.
Each one of those sets is a separate case, and you'll need to tell MVC what to do with each one. You can do this by defining the rule once in the Global.asax.cs file:
For the first case: /blog/year/month/day/title
routes.MapRoute(
"Blog Full Route", // Route name
"blog/{year}/{month}/{day}/{title}", // URL with parameters
new {controller = "blog", action = "post"}, // Defaults
new {year = @"\d+", month= @"\d+", day = @"\d+"} // Constrain parameters with RegEx patterns
);
For second case: /blog/title
routes.MapRoute(
"Blog Title Route", // Route name
"blog/{title}", // URL with parameters
new {controller = "blog", action = "post"}, // Defaults
);
For last case: /title
routes.MapRoute(
"Title Route", // Route name
"{title}", // URL with parameters
new {controller = "blog", action = "post"}, // Defaults
);
The trick is putting theses routes in this exact order, with the least specific at the bottom. Changing the order would result in the wrong route being used (specifically in the last two). If the last case was switched with the second case, URLS of the type blog/SomeTitle would route to the post action with blog as the title.
Whenever you're creating a route for something, keep the following in mind:
- Constraint route parameters with RegEx
- Be
veryaware of route order (which route comes before which) - The squiggly brackets
{something}denote action parameters
Some good tutorials: