title: Plug-in architecture for ASP.NET MVC
body: <p>I've been spending some time looking at Phil Haack's article on <a href="http://haacked.com/archive/2008/11/04/areas-in-aspnetmvc.aspx" rel="noreferrer">Grouping Controllers</a> very interesting stuff.</p>
  
  <p>At the moment I'm trying to figure out if it would be possible to use the same ideas to create a plug-in/modular architecture for a project I'm working on.</p>
  
  <p>So my question is: Is it possible to have the Areas in Phil's article split across multiple projects?</p>
  
  <p>I can see that the name spaces will work themselves out, but I'm concerned about the views ending up in the right place. Is it something that can be sorted out with build rules?</p>
  
  <p>Assuming that the above is possible with multiple projects in a single solution, does anyone have any ideas about the best way to make it possible with a separate solution and coding to a predefined set of interfaces? Moving from an Area to a plug-in.</p>
  
  <p>I have some experiences with plug-in architecture but not masses so any guidance in this area would be useful.</p>