title: TFS: Managing assembly version number?
body: <p>any good approach for managing assembly version numbers in TFS, possibly together with using the same number for the build number?</p>
  
  <p>I would be most interested in an approach that:</p>
  
  <ul>
  <li>Maintains the first three elements of the version</li>
  <li>Counts the rest upward for every "official" build (i.e. a build originating from certain templates only - no need to count up for something like a gated checkin, but the following regular integration build SHOULD count up.</li>
  <li>Labels the builds, so that a manual "release" build can be triggered.</li>
  </ul>
  
  <p>Any solution? How are other people handling this? Right now the (new) TFS is happily building with the same assembly version all around ;)</p>
  
  <p>Something coding the complete assembly version with date etc. is not acceptable - I want that number to "follow rules", and having the date in there is not one of them ;)</p>