title: Interface Reutilization (embedding) for Large Projects
body: <p>First of all, sorry for any english mistakes. Its my first post on Stack Overflow and english is not my native language.</p>
  
  <p>Im facing a problem on a web project being currently developed here at my company. We are making a large overhaul at a legacy application.</p>
  
  <p>The application is being built by different teams in a manner that one team is writing a framework/foundation application that will be consumed by all the other applications (think as modules or even standalone satellite applications). All the applications are currently being written in ASP.NET MVC 3. and the framework (and the others) have views, models, controllers and static resources as any mvc applications (like the login screen, the menus, layouts, etc).</p>
  
  <p>Currently we are organizing the projects like desired using a modified version of the MVCContrib Portable Areas.</p>
  
  <p><strong>My.Framework.Web</strong><br>
  <strong>My.Sales.Web</strong><br>
  <strong>My.Customer.Web</strong><br></p>
  
  <p>The MVCContrib project seems kinda of dead right now and we are looking for other approaches to solve this particular situation.</p>
  
  <p>So my question is: We are doing this the right way? i mean, there is another way to treat a situation where strong interface reuse between projects are a necessity? This seems to me like a common situation but could not find anything similar (on scale) on the internet or books.</p>
  
  <p>Best regards.</p>