InstallAware

Hi Support Team,

I want to convince my boss to move from InstallShield to InstallAware. I already installed InstallAware X3 Trial to be used in conjunction with ContinuaCI / FinalBuilder and was able to build a setup.

Currently there is one drawback against InstallShield, which I want to explain with the following scenario:
- today the mpr file contains the version number (e.g. 3.0.0)
- this file is checked in in our repository
- the created setup.exe contains this version number in its resources (right mouse click, properties, details, file version)

In case we later want to build a version 3.1.0 with just new binaries of the software, there is no need to change the mpr file (besides the version of course) :
- my assumption was that I can provide the version number (3.1.0) via command line and the resulting setup.exe will contain this version
- I found in your forum that I should add something like "VERSION=3.1.0" to the command line, but this will not change the file version inside the setup.exe (it remains to have file version 3.0.0)

It seems that I need to open the mpr file with the IDE, change the file version manually and save the file. After that the automated build process will create the setup.exe with the desired file version.

The setup consists of several Delphi projects. We do not need to open any Delphi project in the Delphi IDE, change the version and save the project before build - the version is provided by the build process.

Is the same possible for InstallAware? Do I oversee something? Is the only way to parse the mpr file during the build process and change the version (e.g. from 3.0.0 to 3.1.0) before I invoke the build command line?

Any help is appreciated.

Best regards
Michael

Dear Michel,

sure you can!

You only need to modify your project, in order to use a "Custom Compiler Variable" to initialize the "VERSION pre-defined script variable" at build time.

Please have a look at following discussion where a ready to use sample is available.
http://www.installaware.com/forum/viewtopic.php?f=2&t=8927

Hope this helps you.

Regards

Dear Francesco,

Thank you very much for your fast answer. It works as desired.

Defining a Compiler Variable and use it as Product Version was my first attempt. But I was advised by a balloon tip, that 'Only numbers and periods are allowed in this field'. This prevented me from trying this approach.

Would you mind to consider not to show the 'Incorrect Product Version Value' balloon tip in case a compiler variable is entered here?

Best regards
Michael