asp.net-mvc-routing

I have a controller called InstallationController , and a fancy report representation of an installation called a Rate Card , but the end user insists on calling installations themselves Rate Cards . I would like him to see the URL http://site/RateCard/Edit/3 , where this gets routed actually as http://site/Installation/Edit/3 . How can I do this in MVC 3 RC2? A couple of options are, you can either rename the controller to RateCardController , or add a new route that directs to the Installation controller, like: routes.MapRoute( "RateCard", // Route name "RateCard/{action}/{id}", // URL with

I am moving from an old site design to a new design with new URL's. All previous page names were static files called PageXX.html, PageX.html, Index.html - where X is a number. My site is now dynamic but I want to trap for those 3 incoming url's and then try and redirect to a certain new page (301 Redirect) else send them to the home page. Do I do all of this in Global.asax or do I just trap those Url's in Global.asax and then route it to a Action and do a 301 Redirect in the Action? Any code examples would help a lot! Thanks EDIT: I think what needs to be done is trap the routes in Global.asax

I am using ASP.NET MVC to develop an application framework. Essentially, the end goal is to be able to log into an admin interface, create a new tenant with custom settings, enable the modules they want (blog, shopping basket, etc)... job done - satisfied customer with new website. I'm not using separate applications because there will be a lot of shared code and it would be easier to maintain this way, and also because it would be pretty easy to bring a new, identical node online at peak times. Depending on what modules are loaded for the tenant, different routes are applicable for each

Q1: So this article says attribute routing is more favourable than conventional routing for api versioning. It's not clear to me the reasons behind such claim because to me in order to support these: /api/v1/products /api/v2/products all you need to do is to define two routes: routes.MapHttpRoute("V1", "api/v1/products", new {controller = "V1Controller", action = "ListProducts"}); routes.MapHttpRoute("V2", "api/v2/products", new {controller = "V2Controller", action = "ListProducts"}); Can something share some insight? Q2: this article says one issue with conventional routing is the order of

I am just getting started with ASP.NET MVC and it's great! However, I don't quite understand setting up routes. How do I route ~/About to ~/Home/About? /Views/Home/About.aspx I would like to be able to access it with /Home/About or just /About If you want to explicity setup a route for it, you can do something like this: routes.MapRoute( "AboutRoute", "About", new { controller = "Home", action = "About" } // Parameter defaults ); I think thats what you want to do? I.e. have /About handled by the home controller? The default route (as below) handles /Home/About routes.MapRoute( "Default", //

[NOTE: I'm using ASP.NET MVC2 RC2.] I have URLs like this: /customers/123/orders/456/items/index /customers/123/orders/456/items/789/edit My routing table lists the most-specific routes first, so I've got: // customers/123/orders/456/items/789/edit routes.MapRoute( "item", // Route name "customers/{customerId}/orders/{orderId}/items/{itemId}/{action}", // URL with parameters new { controller = "Items", action = "Details" }, // Parameter defaults new { customerId = @"\d+", orderId = @"\d+", itemId = @"\d+" } // Constraints ); // customers/123/orders/456/items/index routes.MapRoute( "items", //