We have a product installer using InstallAnywhere that calls another InstallAnywhere installer silently for a different product of ours. After the installation there isn't an entry for the product that was installed silently. Are we doing something...
Is there a known issue with double byte languages on Linux? We are seeing that the InstallAnywhere static strings are all garbage characters for double byte languages on Linux (Red Hat and SUSE). We have InstallAnywhere 2008 Enterprise.
Is there a way to get the Locale object from InstallAnywhere for the chosen language? Currently I am creating a locale object in my custom code using the string I get from the $INSTALLER_LOCALE$ variable. It would be more convenient to use the exis...
We are looking at being able to call our installer silently from another installer (not necessarily InstallAnywhere). I am wondering if there is a way for the parent installer to set the locale of our silent installer to match what the user selected...
If one was to write a custom code rule to be applied against a file in the install phase, is it possible to get the file name and/or path either from a variable or with custom code?
Another option is to create a common merge module and put most (or all) of your files, installer panels, and actions in it. Then create multiple branded parent installers and include the common merge module in them.
You should be able to select the "Launch Notepad" link and click the right arrow button (in the Advanced Designer) to make it a sub-action of the "stuff" folder above it.
I think you'll just have to hard code the paths in your code. For Windows the registry file is in C:\Program Files\Zero G Registry. On 64-bit Windows it is in C:\Program Files (x86)\Zero G Registry. You could use a combination of IA variables like...
You'll have to write a CustomCodeAction that does this. In the code you'll need to check the platform and look for the registry file in the correct path. Then you'll need to parse the xml in the registry file looking for products. Once you get a l...