InstallAware

We use compiler variables for inserting the version number into our command line builds. I made a build just a few minutes before installing InstallAware NX Studio (was previously on the previous latest build - Mooya with just 2 o's?) and everything worked fine. Since upgrading to NX, the compiler variable we use for the program version doesn't put the version in.

Our setup is as follows:
In the Project Properties, we have Product Version: #PROGRAMVERSION#
In some of our dialogs, we show $VERSION$ so the customer can see what version is being installed.
In the MIABuild.exe command line parameter, we have the last parameter: PROGRAMVERSION=4.28.08

When installing the progam, the dialogs display #PROGRAMVERSION# rather than the 4.28.08 they should. Bringing up the properties of the setup.exe, it also shows Program version: #PROGRA

The output from the build includes the following:
Building Project: MyProgram
Output Folder: C:\Users\Me\Desktop\Installaware Builds\Release\SingleDeployment Type: Compressed Single Self Installing EXE
Code Signing: Enabled
Compression: None
Compiler Variables: PROGRAMVERSION=4.28.08,BUILDMODE=SFX,LANGUAGE=English,TITLE=MyProgram,TARGETDIR=$TARGETDIR$,IADIR=C:\PROGRA~2\INSTAL~2\INSTAL~2,PROJDIR=C:\Users\Support\DOCUME~1\INSTAL~1\PARADO~2,IAVER=14.00
###
Cleared output folder C:\Users\Me\Desktop\Installaware Builds\Release\SingleBuilt plug-in action Windows Installer
Built plug-in action .NET Framework
Built plug-in action Windows Installer
Built plug-in action .NET Framework
Copied file ....

While writing this post, I tried making a compiler variable #PROGRAMVERSION# in the IDE, giving it a value 4.0.0, and building it in the IDE (not the command line). It still didn't make it into the final setup.exe.

So it looks to me like the variable is being passed into the build program fine, but the build program isn't looking for compiler variables when building.

Thanks,

Bob

Good morning, Bob.

Does this recent hot-off-the-press thread help?

http://www.installaware.com/forum/viewt ... f=2&t=8791

Hi Michael,

Bother, thought I was first to find that one :-]

Glad to know it's being worked on. Will be back in 24 hours for the patch. Out of interest, I download the whole kit & caboodle (single file install) for our installation. Is it likely to be fixed in an .exe that is in the license file from the MyInstallaware page? (Feel free to answer this after it's released if you can at that stage.)

Thanks,

Bob T