Scott,
We often find the opposite pattern in use: patch AssemblyInfo.cs with the TeamCity-generated build number and there is a <a href="http://confluence.jetbrains.com/display/TCD8/AssemblyInfo+Patcher" rel="nofollow">dedicated feature</a> for that.
As to reverse process, so far you can parse the number in the build script and change the build number in TeamCity via a <a href="http://confluence.jetbrains.com/display/TCD8/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-ReportingBuildNumber" rel="nofollow">service message</a>. A dedicated feature like there is with pom.xml can be finled into the <a href="http://youtrack.jetbrains.com/issues/TW" rel="nofollow">tracker</a>, if you like.
↧