title: How I deal with Visual Studio solution and project files in Git?
body: <p>I usually work with .NET using Git for versioning. In my team, we work in parallel and we often commit our code to integrate in the application. Everything is fine BUT the Visual Studio's solution and project files. We found two ways:</p>
  
  <ol>
  <li>Never commit those files, everyone has his own</li>
  <li>Include those file in the version system</li>
  </ol>
  
  <p>Both ways have pros&amp;cons, but basically we struggle every time we pull from central repo. Here some spare issues we found: (in parentesis, the reference to the above list)</p>
  
  <ul>
  <li>We have to include other's files in the project (1) or include our newest (2)</li>
  <li>If we work on different architectures (x86/x64) we have to manually change <code>.csproj</code> files (2)</li>
  <li>Same issues replied for references and NuGet packages</li>
  </ul>
  
  <p>and so on. <strong>Is there a proper workflow I can use?</strong></p>