protected void Application_Start(object sender, EventArgs e)
void RegisterRoutes(RouteCollection routes)
Sure, this is how we name them on a technical level. Our UX will come up with friendly names. Just like Controls vs. Widgets :)Greetings,
The routing engine is yet another approach for handling web requests. It provides a more coherent and flexible way to handle requests then URL rerating engines, but in its essence does the same thing. I’m not sure I understand correctly your scenario, but it seems the routing engine is the right way to go.
Below is an example how you can modify routes in Sitefinity:
All the best,
Q1 release is scheduled for April 13th. Routing is available from the first release of 4.0 and there i
s nothing new in the upcoming Q1 release in that regard. The features that Georgi is talking about are already completed and definitely will be available in Q1.
To clarify a bit on the features, they represent user interface for setting simple URL rewrites and redirects. These features allow you to do mappings of old URLs to new ones or have additional URLs for the same content. If you want to apply some rules or extend with additional logic you have to do it either by adding custom routes or configure IIS rewriting engine.