In addition to just routing resources, having the concept of end-to-end resources would be a good thing. Then you could for example have a RESTful resource generator ala Ruby on Rails that automatically generates a model (with migration), views, controller, and tests for a "resource" would be a big time saver. With Rails you can run something like:
rails generate scaffold User name:string email:string
And have the model, migration to create that model in the database, views, controller with CRUD actions, tests, and other scaffolding files generated for you in the correct places in a working way. It's a very fast, low friction way to work.
Right now with ASP.NET MVC you have to piece this together in multiple steps (in part because of a lack of standardized integration with the model layer, which could ideally default to EF Code First out-of-the-box to make a more streamlined experience ala Rails). Plugging in a way to generate a full stack "resource" in a single step would be a big win. Obviously there are a lot of different options for what someone might want to use for various pieces. But creating some standardized infrastructure for generating this full stack, and then letting people choose their own default Model, View, and Controller options (via T4 templates?) could hopefully accommodate that.
khalid abuhakmeh commented
Checkout out RestfulRouting.com, I am the manager of this project but feel it makes a great addition to the ASP.Net MVC stack. It is opinionated but does not hinder you from making any routing decision you would like.
Jakob Strauch commented
... and a HAL formatter :)
Soe Moe commented
I think it is rails-like RESTful Resource Routing. +3 votes.