InstallShield Legacy options has no affect

FinalBuilder Bugs
1

The following 3 proprties in the InstallShield Legacy tab (under Tools->Options) has no affect:
1. IFX Location
2. ISRT Location
3. Include Path

It seems that the action ignores the proprties that are defined in the InstallShield Legacy Tab and uses only the proprties in the Compiler tab of the actual action.

InstallShield version used: IS 6.3
Final Builder version used: 6.3.0.1506

2

Hi Nir,

Unfortunately the use of option values in this action is a bit different to most actions in FinalBuilder in that the values specified in the global options are used only to pre-populate the fields in the action when it’s added to the project, they are not used at runtime. You’ll need to make sure that the fields are set in the action rather then letting it fall back to the global options. We had a discussion about changing the behaviour so that it matches the rest of the actions in FinalBuilder but are concerned that changing it now has the possibility of being a breaking change.

Regards,
Paul.

3

Hi Paul, thanks for your quick reply. I understand your concern regarding breaking the compatibility, however the current state doesn’t meet the purpose of the global properties.
As i understand it, the action properties are used to define project specific properties while the global properties allow you to define “Component” global properties. let me explain by an example:
In the global properties of Visual Studio .Net component i can set the various paths that are required to locate the Visual Studio executable. Setting this globally allows the members of my team to install Visual Studio to any path that they desire; they simply need to configure their Final Builder global settings once.

The InstallShield action requires both project depended objects and InstallShield engine objects. Due to the fact that the global properties are not available, we are required to enter the path to the InstallShield engine objects in the actual action; thus we must force all team members to Install and maintain their InstallShield engine in the same location.