title: Best Practice for multiple asp.net web applications
body: <p>Looking for the best practice when having multiple web applications within one ASP.NET "site" or "solution". I have a few options I am toying with:</p>
  
  <ol>
  <li><p>old faithful of putting all applications and Site master into one Solution / one web application</p></li>
  <li><p>My boss is worried about having 30 'applications' that are all under the same project in VS and every time we make a change to one have to deploy to all. So this makes us want to break out each into a separate project under the same solution. This makes us have to look into Master page solutions</p>
  
  <ul>
  <li>Master page needs to support dynamic menu structure. Is this something that I can do with a single SiteMaster? Does VirtualProvider provide the right solution for this? Anyone have any good tutorials on it? </li>
  </ul></li>
  <li><p>Creating a UserControl for each application and reference it in the main application</p></li>
  </ol>