asp.net-mvc-routing

I would like to display the view in the folder if no controller/action matches. For example www.site.com/Home/Index, if I have the normal default route {controller}/{action}/{id} then I need a HomeController with method Index. And there is a folder in Views folder called Home and the file Index.cshtml If i try www.site.com/About/Index i need to create the AboutController and the method index. But I have just the folder About and file Index.cshtml. I would like that if the default route does not match but I have a Folder and a File in the Views folder that match the patern: {controller} is the

I have a product category table to represent a hierarchical category structure, a typical Parent-Child relationship table in the database. Fill it with Guitar Center's data as an example: If you render them to a page with <ul> and <li> : Texts in blue are the URLs I would like to generate. For any given category, the link consists of its slug and its parents' slugs. Note that the example I listed only has 2 parent-child levels. In theory, with the self-referential structure, any child could have infinite parents. Questions: How to set up routing template to achieve that? If the routing

This question already has an answer here: Route controller that is in a sub folder 2 answers In my Controllers folder i want to have a subfolder called Admin. When i go to http://localhost:port/Admin/Login/ it says the page could not be found. RouteConfig.cs using System.Web.Mvc; using System.Web.Routing; namespace ICT4Events { public class RouteConfig { public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( name: "Default", url: "{controller}/{action}/{id}", defaults: new { controller = "Home", action = "Index", id =

I'd like to handle URLs like this: /Id/Key1/Value1/Key2/Value2/Key3/Value3/ Right now, I have set up a rule like this: /{id}/{*parameters} The parameters object is passed as a single string to all the actions that are involved in forming the response. This does work, but I have a few problems with it: Each action must resolve the string for itself. I've, of course, made an extension method that turns the string to a Dictionary<string, string> , but I'd prefer it if the dispatching mechanism gave my methods a Dictionary<string, string> directly - or, better yet, the actual pairs as separate