What, you thought I was done with Dynamic Routing?  No way!  My previous Dynamic Routing system was only a stop gap, allowing only NodeAliasPath routing, and a rather clunky redirection system.  After 80+ hours of work (and 20 some from fellow Kentico enthusiast Sean G. Wright), we present to you the fully integrated and optimized Dynamic Routing plugin!

THIS POST IS OUDATED, PLEASE SEE NOVEMBER 2019

MVC Routing operates on the basis that a request is handled by Controllers and Actions in predefined routes. Dynamic Routing is where a request maps to a Page (TreeNode), and that Page's settings (Template, Page Type) determines how the request should be handled (which Controller/Action/View). In Portal Engine, the Url matched the NodeAliasPath or Url Aliases of a page, and the Page's Template then determined how it was handled. In this article we will outline how to restore the Portal Engine request handling now that the Kentico 12Service Pack is out.

Things have been moving along in the Kentico MVC world.  As an MVP I was priveledged to get a preview of the upcoming Service Pack and we have the green light to share that with you.  I also have worked on another improvement to restore some of the Kentico Portal Engine functionality that I'll go into depth explaining.

Portal Method and MVC can be pretty differnet animals.  In this article I'll show you how make your MVC site find pages based on their NodeAliasPath or Url Alias, and render them how you wish!