Nothing has changed in it, if it worked before it should work now as far as I know. It isn't something used currently in features we ship but it worked when I implemented it way back and it hasn't been changed so it should still work as far as I know.

It would require adding this in user.config since it is disabled by default given that we don't use it for anything we ship.

<add key="EnableRouting" value="true" />

and of course changes in user.config are not automatically detected so you must also touch web.config after adding that setting.

The main reason we don't use routing for anything important in mojoportal is because routing is pattern based and since we support multiple sites based on folder names it kind of makes the pattern ambiguous if the root site needs /somefolder/ and but child sites have the first segment as the site folder like /sitefolder/somefolder/ would be the pattern for a folder site. This gives the first segment 2 different meanings so it can't be used very well unless not using folder based child sites, and since we don't want to break folder based child sites we just haven't used routes for anything so far given that our whole url rewriting friendly url system was developed long before asp.net routing ever existed.

I was just going to post a threat on using this as well!  Good timing!  Thanks Joe and John!

No problem Joe! I meant to a couple weeks ago and kept forgetting!  

Thanks much!  The routes are working perfectly for my particular scenario!

Hi John,

In 2.4.0.4 we did change the way routes are registered as we added support also for web api routes and wanted to have a consistent way to register routes. We dropped routing from our .NET 4 build because we use new .NET 4.5 classes for routing and web api.

To plugin custom routes now you implement this IRegisterRoute interface which has methods for mvc routes, api routes and filters to be registered, you can just do nothing in the methods that aren't of interest.

An example implementation is in the mojoPortal.Features project where we add an api route for forum notification moderation.

whatever class/type/namespace where you implement the interface, you plug that in by adding a config file under /Setup/RouteRegistrars that declares the type. 

Then the methods on your RouteRegistrar will be called during application start.

Sorry for the breaking change, I didn't think many people were using the routing feature. It is pretty straightforward to implement the new way. If you have any trouble making the needed changes let me know and I'll try to help.

Best,

Joe