Preventing a Property Value from Being Written in Advanced UI and Suite/Advanced UI Debug Log Files

InstallShield 2015

Project: This information applies to the following project types:

Advanced UI
Suite/Advanced UI

If you launch an Advanced UI or Suite/Advanced UI Setup.exe file with the /debuglog parameter, the Suite engine generates a debuglog file. By default, the debug log file includes the values of changed Advanced UI or Suite/Advanced UI properties.

In some cases, you may want to prevent the Suite engine from writing the values of specific properties to the debug log file. For example, you may want to prevent properties that contain passwords and other sensitive information from being logged.

To prevent a property from being written in the log file:

1. In the View List under Behavior and Logic, click Property Manager.
2. In the Name column, find the ISHiddenProperties property.

If this property is not listed, click the New Property button to create this property, and in the Name column, enter ISHiddenProperties.

3. In the Value column, enter the name of the property whose value you do not want to be logged; ensure that you use the same capitalization. To list more than one property, separate each with a semicolon (;).

Note that ISHiddenProperties is useful for prevention of logging for values in the following scenarios:

The value of the property changes.
The end user sets the value of the property through command line when launching the Advanced UI or Suite/Advanced UI Setup.exe file.
The property is configured through a command line that the Advanced UI or Suite/Advanced UI installation passes to a package. This is configurable in the Packages view, on the Common tab, in the Operation area.

If the property is logged through ISuiteExtension::LogInfo, the Suite engine cannot prevent the logging. Therefore, any code that you create to write a property value to the log file should read ISHiddenProperties to see whether the property value should be logged.

See Also