title: What's the Best Practice for incorporate Semantic Versioning using TeamCity
body: <p>TeamCity is a great CI tool and we also use Semantic Versioning to manage our DLL version for a long time, now we are reaching a idea to integrate TeamCity and Semantic Versioning together, meanwhile we do some research on this topic, Let's say the Version infor like </p>
  
  <p>MajorVersion.MinorVersion.PatchVersion.BuildNumber</p>
  
  <p>The buildNumber we always use teamcity buildnumber, and other 3 versions we maintains within assemblyinfo.cs
  the question here is - how can we use teamcity to feed its build number into assemblyinfo.cs, i can find Msbuild support this parameter, and is there any best practice to handle the same thing? and we also would like to feed the whole version into nuget packs as the published version information to our developers</p>
  
  <p>Thanks a lot</p>