title: Xamarin mobile app version number scheme across 3 platforms
body: <p>There's probably multiple questions here all related. I'm trying to come up with a simple version number update scheme for our 3 mobile apps built from a single xamarin solution.</p>
  
  <p>What I'm looking for is a simple way to keep all these values in sync with one another without having to go around and update them all individually.</p>
  
  <ul>
  <li>Windows Phone Version should get set to the AssemblyVersion or FileVersion Automatically</li>
  <li>IOS Version Number should be set to same. (not sure what the build number should be)</li>
  <li>Android Version Name should be set to same.</li>
  <li>Android Version Number should auto increment for each release build.</li>
  </ul>
  
  <p>My current setup requires navigating around to 4 different places to manually sync up the version numbers.</p>
  
  <ol>
  <li>Global Assembly Info</li>
  </ol>
  
  <p>I have a linked file which contains the AssemblyVersion and AssemblyFileVersion that's shared by all PCL and Platform projects in the solution with the following info.</p>
  
  <pre><code>[assembly: AssemblyVersion("2.1.1.*")]
  [assembly: AssemblyFileVersion("2.1.1.0")]
  </code></pre>
  
  <ol start="2">
  <li>Android</li>
  </ol>
  
  <p>Seperately under the android project, I have to manually update the version name and version number (int)</p>
  
  <pre><code>Version Name: 2.1.1
  Version Number: 2
  </code></pre>
  
  <ol start="3">
  <li>IOS </li>
  </ol>
  
  <p>Under the iOS Application tab, I've 2 more fields to fill in.</p>
  
  <pre><code>Version Number: 2.1.1
  Build Number: 0 //Not sure if I'm using this field correctly.
  </code></pre>
  
  <ol start="4">
  <li>Windows Phone</li>
  </ol>
  
  <p>On the "Packaging" tab of the WMAppManifest Property dialog, I have to supply a Version Number as well.</p>
  
  <pre><code>Version Number: 2.1.1.0
  </code></pre>