title: visual studio git solution project madness
body: <p>So i'm trying to figure out how best to structure my git repositories with my .net web application projects and database projects while using git and am really struggling. </p>
  
  <p>We are using feature branching workflow and continuous integration with dev and master main branches currently.</p>
  
  <p>So here's the scenario... 
  say i have 6 projects.(3 web and 3 database) </p>
  
  <p>websiteA (has queries to database1)
  websiteB (has queries to database2)
  websiteC (has queries to database1, database2, and database3)</p>
  
  <p>database1 (references database2)
  database2 (references database1)
  database3 (references database1 and database2)</p>
  
  <p>all projects are deployable independently although there are many times where they need to deploy together.<br>
  (yes i know this is a mess and needs to be cleaned up). </p>
  
  <p>My question is how would you structure the git repos. 
  Here are a few options I have considered. </p>
  
  <ol>
  <li><p>Git repo with solution for each? seems like this would be more modular and less noisy in the repo but more coordination is needed when pushing db and web code.</p></li>
  <li><p>one big git repo with all the projects in them? 
  seems this is a bit easier to be able to work across multiple projects concurrently without having to synchronize so much. </p></li>
  <li><p>git sub modules or git subtree? (worried about these as many of the developers are new to git and these seem to be a little more complicated to me).</p></li>
  <li><p>other options? 
  Any thoughts? Appreciate your help. </p></li>
  </ol>