I was hoping you wouldn't say that.

I have uploaded two bare-bones installers for reproducing this issue and have uploaded the project used for building the installers. *Note: I used the multi-instance project, but I made a slight alteration. The upgrade installation will "overwrite" the original installation. You will not s...

I built my setup using the command-line, with the BUILDVER compiler variable. After executing my setup, I checked ARP and the version # of my setup appearing in ARP is the same as the version # I set to the BUILDVER compiler variable. As a possible workaround, instead of setting VERSION to your BUIL...

Yes, I had to write the DisplayVersion value. I am using InstallAware 8, which doesn't write the version of the setup. I have to explicitly write the DisplayVersion. I believe in InstallAware 9, this issue was fixed. The logic I used in my example and the logic you described in your initial post sho...

I set the version of my setup to 1.0. In the script, I set the VERSION pre-defined variable to 2.0. After installing my setup, I went to ARP and the version of the installation is 2.0. Now, I set a compiler variable, BUILDVER to 2.0, and in my code, set VERSION to #BUILDVER#. When I ran my setup, I ...

I mean localized for different languages, such as Portuguese or Spanish. If you change values stored in variables after localizing your installer, you won't see what you changed because the string files will contain the original value at the time you localized your installer. (It is rather complicat...

Is your installer localized?

In order to set the version # of your product in ARP, you need to set the DisplayVersion value in the registry, under \SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$TITLE$.

If I change the product version # in the installer, performing an upgrade on a previously released version of the same installer prompts a message saying "The feature you are trying to use is on a network resource that is unavailable." The message then proceeds to instruct me to click OK t...

I am not talking about the buttons on the dialog. I am talking about the Display Dialog command in your code. In the section of code for displaying the Database dialog, you have an if statement checking if the variable MAINTENANCE doesn't equal True. Therefore, if MAINTENANCE doesn't equal true, you...

I also check for the existence of QuickTime, but instead of looking for \\..\\QuickTime\\InstallDir, I look for \\..\\QuickTime.

However, in my experience with QuickTime, it is possible for the key to exist and the QT player to not exist.

The Copy/Move actions are cached and when Apply Install is executed, the Copy/Move actions are performed.

Yes, you can use variables in the source/destination locations. However, variables cannot be used for the source file(s).

On your custom dialog, set the .text property of the control to the variable that will hold the data from the registry.

for example:
Read Registry HLKM\\..\\..\\TestValue into REGVALUE

on your custom dialog, set the control property to $REGVALUE$

In the Display Dialog command, did you leave the "Return Result in Variable" blank? If so, make sure to set it to WIZARD. I was able to reproduce your problem by leaving it blank.

Read the help file for creating shortcuts. You will notice under the Icon File Path section that the icon path has to point to the icon file on your system.