At 3/22/2004 10:14 AM, Jason Teagle wrote:
>Something has just come to light, and I wondered what others did. > >We have a policy of numbering our works in progress and their proper >counterparts like this: 1.5 beta 01, 1.5 beta 02, 1.5 beta 03, then comes >1.5 (the real thing). This seems to make sense to me, since the earlier >parts are betas of 1.5, not of 1.4. > >I was coding this into the version resource as 1.5.1.0, 1.5.2.0, 1.5.3.0 and >then 1.5.0.0 (reserving the last digit group for special builds). But it has >just occurred to me that installers such as Inno Setup, when using this >version resource to decide whether to install a later version, is not using >the same - when you look at it in version resource format, of course 1.5.0.0 >looks older, so it will not be installed over the top.
x,y,z,b
x is the major version 10 15 etc y is the minor version 5, 20, 55 etc z we don't use b is the build number starting at 1 and incrementing with every build
The first 2 numbers never change during a product's lifecycle.
The shipping product has the highest build number to that point.
That way it will install over any betas
Phil Daley < AutoDesk > http://www.conknet.com/~p_daley
