SB10 Tips & Tricks #3: Automating Version and Build Numbers

[NewsArchive]

-- SB10 Tips & Tricks #3: Automating Version and Build Numbers

The version and build number keys respectively specify the marketing and
internal versions of your setup application. The "auto generate version
number" feature in SetupBuilder 10 generates the major version, minor
version, build number, and revision number for you, and increments the
numbers each time you select "Compile".

-- How do I auto-increment my build numbers using SetupBuilder 10?

1. In the Script Editor, add a "#build version increment..." compiler
directive. "Compiler Variable" is the name of the compiler variable that
holds the new version number. For example: [MY_PRODUCTVER]. "File Name"
is the name of the version text file that stores the version information.
The File Name field contains the location of the file in the local file
system. For example: [SB_PROJECT]\MyBuildNumber.txt specifies a file in
the same directory as the project file.

2. Create a "MyBuildNumber.txt" ASCII text file. This function requires
the following Version Info File format (text format):

;This will increment the version build number by 1
;FIRST RESULT: 10.0.5001.0
[build]
increment=0.0.1.0
version=10.0.5000.0

;This will increment the version build number by 10
;FIRST RESULT: 10.0.5010.0
[build]
increment=0.0.10.0
version=10.0.5000.0

;This will increment the version build number and revision by 2
;FIRST RESULT: 10.0.5002.2
[build]
increment=0.0.2.2
version=10.0.5000.0

3. Use the compiler variable [MY_PRODUCTVER] where you need it. For
example, in "General Information" -> "Product Properties" -> "Product
Version [PRODUCTVER]".

--
Friedrich Linder
Lindersoft | SetupBuilder | www.lindersoft.com
954.252.3910 (within US) | +1.954.252.3910 (outside US)

--SetupBuilder "point. click. ship"
--Helping You Build Better Installations
--Create Windows 10 ready installations in minutes
--Official COMODO Code Signing and SSL Certificate Partner

[NewsArchive]

In addition to that, I found this helpful (no matter how you build your
version numbers):

1) Use the #get file info (File version) function and put it in a variable.
2) Use #msg "New Build: [PRODCUTVER]" [Clipboard]

When I deploy a new version I send a mass email out to clients and I
simply paste the above as the subject line and then proceed to list the
fixes and features in the body of the email.

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Very cool, Russ. Thanks for sharing!

Friedrich

[NewsArchive]

Sounds like something you could do at www.deploymatic.com.

Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
I'll search help files & Google for you.

Grammar troll's, are the worse.

[NewsArchive]

Hi Jeff,

>
> Sounds like something you could do at www.deploymatic.com.
>

Hmmmmmm, excellent idea !!!

Thank you!

Friedrich

[NewsArchive]

Hi Friedrich,

> -- How do I auto-increment my build numbers using SetupBuilder 10?

I let Build Automator do all versioning for me so that everything in
every build has the same version information, code, templates, help,
install, version control, everything I set up version variables in
each BA script and then increment them appropriately. I only use the
first 3 sections of the version number, as in 1.1.1. Each time I build
the last number is increased so it goes to 1.1.2. Of course I can set
those variables to any number I want at any time if I want to skip
ahead When I initially commit the project to repository (before I
start the actual build process) I get the build number from TortoiseSVN
and then add it as the last item in the version string. I then use this
in search/replace actions in my code/templates, send variables to
Help&Manual and pass it on to SB using a Compiler variable to receive it
in SB.

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

[NewsArchive]

Hi Friedrich,

> -- SB10 Tips & Tricks #3: Automating Version and Build Numbers
>

http://www.icetips.com/showarticle.php?articleid=1568

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC