title: ASP.net MVC and modularity
body: <p>I'm trying to find out if there is a way to use ASP.Net MVC to design a modular web application.</p>
  
  <p>By modular, I mean that I should be able to drop a "package" (which could be made of a bunch of files, I don't necessarily require a single file deployment).
  The idea is to deploy additional functionality seamlessly. Functionality could go from tweaking the existing web site (that is the easy part, any plugin architecture would do), up to having whole new site areas.</p>
  
  <p>I'm looking for pointers as to 
  - if that is even possible
  - what choices I have to make w/ regards to view engines for example
  - any gotchas I should be aware of</p>
  
  <p>I found one or two references, but ASP.Net MVC moves fast and they might be out of sync.</p>
  
  <p>Any input is welcome (up to and including "don't go there") !</p>