title: Avoiding merge problems when sharing solution between Xamarin Studio and Visual Studio
body: <p>When sharing a solution between Xamarin Studio and Visual Studio, changes to solution/projects leads to unexpected results. The source text of the <em>.sln/</em>.project files has unexpected modifications, e.g.</p>
  
  <ul>
  <li>UUIDs changed from lower to upper case</li>
  <li>Reordering of lines in the .sln file</li>
  <li>Changed "ToolsVersion"</li>
  <li>Changed "Visual Studio" version</li>
  <li>Other changes, like changing line break, changed "true" to "True", ...</li>
  </ul>
  
  <p>This e.g. happens when changing the startup project, adding referenced projects, building the solution.</p>
  
  <p>These changes lead to a "commit ping pong" between Xamarin Studio and Visual Studio users, and make merging harder. We experienced this problem with Xamarin Studio 5.5.4 and Visual Studio 2013 Update 4. The <a href="https://github.com/perpetual-mobile/SharingXamarinSolution" rel="noreferrer">https://github.com/perpetual-mobile/SharingXamarinSolution</a> repository contains examples. The <a href="http://forums.xamarin.com/discussion/comment/95851" rel="noreferrer">http://forums.xamarin.com/discussion/comment/95851</a> thread also describes this issue.</p>
  
  <p>How can this problem be avoided? Is it possible to prevent this from happening when using only Xamarin Studio and Visual Studio? Or do we need an additional tool (like e.g. <a href="http://www.cmake.org/" rel="noreferrer">cmake</a>)?</p>