Making the drops location for a TFS build match the assembly version number
A couple of years ago I wrote about using the TFSVersion build activity to try to sync the assembly and build number. I did not want to see build names/drop location in the format ‘BuildCustomisation_20110927.17’, I wanted to see the version number in the build something like ‘BuildCustomisation 4.5.269.17’. The problem as I outlined in that post was that by fiddling with the BuildNumberFormat you could easily cause an error where duplicated drop folder names were generated, such as ...