ISBP10

InstallShield 2016

Project • This information applies to the following project types:

Message (Warning)

AppSearch [1] uses insecure custom property [2]. Its value may be unavailable to the execute sequence.

[1] is the name of a system search in your project, and [2] is the name of a property that is used by that system search.

Description

If you set a public property in the user interface sequence of an installation that requests elevated privileges for the execute sequence, and you want to pass the property’s value to the execute sequence, the property must be listed as values for the SecureCustomProperties property, or it must be a restricted public property. Therefore, ISBP10 verifies that if the AppSearch table in your project contains custom public properties, the custom public properties are listed as values for the SecureCustomProperties property. If the custom public properties are not listed in the SecureCustomProperties property, the warning occurs to alert you that you may need to take steps to allow a property’s value to be passed to the execute sequence.

Corrective Action

If you do not need to use the property in the execute sequence, you can disregard the warning message. However, if you do need to use the property in this sequence, you need to resolve the warning.

To resolve this warning, open the Property Manager view. For the Value column of the SecureCustomProperties property, add the name of the property that is mentioned in the warning message. If this property contains more than one property, separate each one with a semicolon (;).

See Also

Property Manager View

Adding a System Search

SecureCustomProperties Property (Windows Installer Help Library)

AppSearch Table (Windows Installer Help Library)

Requirements for the Windows Logo Program

InstallShield Best Practice Suite

Open topic with navigation