"Modeling" ASP.Net MVC Routes
I am working on demo/talk for an upcoming event (more on that later).
In the process of doing that I was modifying our “MService” implementation and thinking about ASP.Net MVC Routes.
I happened upon an article that I think proves out another pragmatic aspect of our approach and foreshadows some of the things that we have been working on.
http://www.iansuttle.com/blog/post/ASPNET-MVC-Store-Routes-in-the-Database.aspx
An immediate beef I have with ASP.NET MVC is defining the routes in the Global.asax.cs… I can’t change routes without recompiling and deploying code. I thought it better to configure routes in a more dynamic environment, specifically the database, which is what this post will provide an example for.
Now imagine all that using “M”, particularly in conjuction with a DSL that allows for programmatic actions — not just config.