Why are build numbers limited to 65535?

How to deal with the Y2K7 problem -- file versions and AssemblyInfoTask

Buck Hodges — Sun, 07 Jan 2007 04:44:02 GMT

If you use the AssemblyInfoTask to stamp the version numbers for your assemblies that you build with

VSTS Build gernerates error CS0647

Christian Binder's Weblog — Wed, 10 Jan 2007 17:11:48 GMT

Sie erzeugen tägliche Builds in VSTS und nutzen den AssemblyInfoTask , um die File und Assembly Build

re: Why are build numbers limited to 65535?

Eric Lee — Sat, 13 Jan 2007 22:26:44 GMT

Great explanation, thanks for the details!

re: Why are build numbers limited to 65535?

Mark — Wed, 17 Jan 2007 01:11:49 GMT

I made a patch for the zip task to canonicalize the working directory path, but I can't seem to get a hold of you guys. Recommendations?

re: Why are build numbers limited to 65535?

Mark — Wed, 17 Jan 2007 01:12:39 GMT

er... is this the community tasks blog, or the msbuild blog?

re: Why are build numbers limited to 65535?

msbuild — Tue, 30 Jan 2007 00:16:16 GMT

Mark, this is the msbuild team blog, not the community tasks blog.

Neil

re: Why are build numbers limited to 65535?

Dan Trietsch — Mon, 26 Mar 2007 20:26:46 GMT

Could use YY + ordinal days (days since 1/1) ; such that, March 26, 2007 build would be: 1.0.07084.00

re: Why are build numbers limited to 65535?

chha — Tue, 24 Apr 2007 10:45:19 GMT

I am terribly sorry guys, but you are all wrong: The highest valid build number is not 65535 (but you were pretty close: it's 65534. But don't ask why, 65535 throws an exception, 65534 does not...)

re: Why are build numbers limited to 65535?

Bryan Garcia — Sat, 25 Aug 2007 01:54:08 GMT

Neil,

As per the Practices (How to Modify the Build Number) in the TFSGuide we should override BuildNumberOverrideTarget to synchronize the TFSBuild number with the Actual Assembly version. This cant be done with your current method since the Assembly info task has 2 steps or tasks merged in one. I should be able to generate the Assembly Version and Information and then before compiling, copy it to the file. This is as I said before is done in one single step inside the Execute for the task. I'm modifying the source code to create two diferent tasks one that will generate the Version and Assembly info, and the other that will write to the corresponding assembly files. I will generate the Assembly version and information on BuildNumberOverrideTarget and then on UpdateAssemblyInfoFiles only will copy the previously generated Assembly Version and info to the files (no increment will be done in this step) this will require of course modifications to the VersionNumber.targets file. My question is, are you guys planning to do this? I have seen various posts asking for this, and in the TFSGuide they explicitly talk about it, but they dont actually provide the implementations for the tasks, its like it assumes that the reader knows that he has to implement that task.