title: How to design a plugin architecture for ASP.NET with MVC Web application
body: <p><strong><em>Introduction:</em></strong>
  Now I know this question could be very broad and it would be too hard to answer without me asking something specific.   So All I ask is just some direction, or a brief high level explanation of a design, or maybe there is already some framework out there that could help me get started...I'm not sure..   I have never designed a plugin architecture before, so maybe there is some resource/example you could point me to on the web that would help me learn so that I may come up with my own solution.</p>
  
  <p><strong><em>Details of my question:</em></strong>
  My intention is I would like to create a plug-in architecture for a new pet-project that I am building in ASP.NET MVC.</p>
  
  <p>I would like to design it so that it has some sort of plug-in ability for all, or at least most, of the application's components.  </p>
  
  <p>The reason I would like to do this, is so that I may be able to do deployments with nearly zero down time.  The idea is that when I want to deploy the latest version I would drop in the new DLLs into a specific folder, and the application would load up the new plug ins and that is it.</p>
  
  <p>For exapmle, lets say I add a new "contacts" feature to my web application where users can search, add and delete contacts.  I would like to be able to deploy that by way of plugins.</p>
  
  <p>Is something like this even possible for Web Applications? Or am I just dreaming?</p>