title: Best Practices Using Git with Visual Studio?
body: <p>I'm considering migrating from Subversion to Git at work, and would like to get opinions about the best way to set up Git on Windows, and any problems that might arise from the combination of Visual Studio and Git.</p>
  
  <p>The current setup is TortoiseSVN, with Visual Studio 2008 and AnkhSVN for .NET applications. The replacement would probably be <a href="http://code.google.com/p/gitextensions/" rel="noreferrer">Git Extensions</a>.</p>
  
  <p>Advice on repository layouts would be particularly appreciated. All of our solutions use multiple projects, and we now have a number of custom assemblies that we will need to share between applications. The current layout of our Subversion repositories definitely isn't optimal.</p>
  
  <p>UPDATE: I've now migrated to Git using Git Extensions, and it's working very well. Shared code and assets live in separate repositories and are used as submodules. I found submodules slightly confusing when I started, and <a href="http://gaarai.com/2009/04/20/git-submodules-adding-using-removing-and-updating/" rel="noreferrer">this post</a> was very helpful.</p>