Hi Francesco, Yes, the debug message displays but it displays before the sample AIR is fully finished being installed. I noticed the desktop icon for the sample AIR app appears after my debug message appears, which, in my opinion means the sample AIR app hasn't quite finished installing. Without tha...

Hi Francesco, Here is a test project. Before the Welcome dialog appears, it will check if Adobe AIR exists on the user's system. If it doesn't exist, the installer will install it. Then it will proceed to install a sample AIR application, by invoking the Adobe AIR runtime. I have a debug message dis...

Hi Francesco,

Thank you for the quick response!

Yes, I made sure to set the "Wait for Program to Finish" flag. This is a critical aspect of the Run Program command.

I have an installer set up to install my AIR application. In order to install my app, I first need to install Adobe's AIR runtime and then use the runtime to install my app (I need the AIR runtime to install my app silently). I have the Run Program command set to execute the AIR runtime with all the...

I have localized my installer for Arabic speakers. All my installer dialogs appear just fine, except for the message boxes. A few of my message boxes contain English text in the Arabic string and when the message box is displayed, the Arabic text doesn't appear correctly. All my strings were localiz...

When the user selects their destination, use the Does File/Folder Exists command on $TARGETDIR$\appname.exe. If the app exists in the target directory, display a message telling the user to select a new directory and after the user dismisses the message, reload the destination dialog.

View http://www.installaware.com/forum/viewt ... a3a1905a73

You would have to add the version number manually in the project settings every time you build your installer. You cannot use variables in the output file name. The best way is to use the command line for building your installer. Then have a script get the version number of your product and add it t...

Hi, I built a stripped down installer project which includes a file (named FileA) that is dated 8/11/2009, made sure that it does not overwrite the same file if it exists on the target system and installed. I, then, rebuilt my installer but this time I used a newer version of FileA, which is dated 4...

Use the command Delete Files Recursive. Make sure to include "\*" when you pass the directory. For example: $TARGETDIR$\*

According to jimo, the product codes need to match. Does the installer look in the registry for the product code of the previous installation or does it look somewhere else?

Do you know why this happens?

zchris,

Have you thought about adding Unicode support to your EditFile plugin? This would be really useful.

My installer is localized in a few languages. When I make any changes, like adding or removing commands and files, do I need to localize every time I make a change?

You need to write the version number to \SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\<product name>\DisplayVersion.