.NET 4.0 MEF. ASP.NET MVC 3.0 Pluggable Approach

Question

I am going to launch a new MVC 3.0.NET 4.0 application.

I want to implement each component for my website once and just reuse it for the other websites that I am going to create.

I am currently looking for the best practice that I can use to achieve my goal.

I did some research and found that I can take advantage of many benefits with MEF.

I found an interesting MEF MVC solution called plugable MVC http://www.thegecko.org/index.php/2010/06/pluggable-mvc-2-0-using-mef-and-strongly-typed-views .

Is it really worth using this approach (Plugabble MVC) to create MVC applications?

Advantages of the disadvantages of pluggable MVC?

Can anyone suggest something else?

Answer 1

What specific problem are you trying to solve? MVC is a very extensible and pluggable framework. I would say that for a simple site MEF is not required. Please provide additional information about the problems you are facing with the MVC database.