asp.net mvc area - best prectice

Question

I'm currently building a CMS system, and I need to have an easy way include or exclude components.

My first think was to use asp.net mvc area feature, to identified each component on itself.

But from what I see, the area feature has problems, so maybe it not that good idea.

What you guys think? What ways we have in asp.net mvc achieve this behavior?

Answer 1

After a few experience with area feature, I think that areas are best for something entirely different in your site, that not share the same master page with the root area.

In my case, that components are an add-ons to the root site, and share the same master page, it not best practice to use areas.