I'm looking to ideas on how best to implement persistent but incremented build numbering between product releases. Our products are versions as follows: "...". The main reason for doing this is to track the build of the product through BETA and onto maintenance release, i.e. we need to track the daily builds and stamp each binary file/docs.
We don't want to use MSBUILD, so the idea I'm toying with is to use a FB variable that increments each build and uses property sets to update our C++ and C# resources, i.e. x.y.z.. As part of this we could change our source code to read the version resource for display and log file purposes, and update docs etc.
The one downside is we have 30+ Visual Studio projects that would need property sets applied to.
A simple solution to this is to store the build numbers in an ini file, and then load the value into a variable at the start of the build, increment the variable at the end and save the variable back to the ini file. This is how we manage the finalbuilder build numbers, it’s worked well for several thousand builds over the last 10 years
Do you reset the build number after each major or minor version?
I haven't tried yet, but can variables be used in a propertyset to update the file version resource, i.e. File Version, Product Name, and Product Version?
BTW - You should do a knowledgebase article on some build number scenarios as I'm sure it would interest a lot of people.