I probably spoke or mentioned of this before, however I really started to use Phil Haacks â€˜Controller Groupingâ€™, aka â€˜Areasâ€™ sample code â€“ and I really like the concept.
Iâ€™m using this currently to consolidate my library of html helpers, to build up samples of using asp.net mvc with jQuery, ExtJs, etcâ€¦
The beauty of this is how â€˜pluggableâ€™ areas are â€“ each with their own set of unique files: controllers, views, models with a centralized way of accessing them.
As a former Monorails user, I find it extremely important and hope that this is actually built into asp.net mvc.
The scenario that areas address is being able to partition your application into discrete areas of functionality. It helps make managing a large application more manageable and allows for creating distinct applets that you can drop into an application.
From the blog you can download a sample prototype here.
Iâ€™m going to continue building up my â€˜samplesâ€™ project with areas and see how it plays out, any gotchaâ€™s on the way, etcâ€¦
Iâ€™d say that even if you donâ€™t use the areas, building this in as a easy way to expand your solution is a great concept.