cancel
Showing results for 
Search instead for 
Did you mean: 

Build Warning -5031

Build Warning -5031

Summary

Possible causes of Build Warning -5031

Symptoms

Build indicates:
ISDEV: warning -5031: The icon for the setup.exe could not be updated. Setup.exe will use the default.

Cause

The fully qualified name of the file that contains the icon was not specified to use your own icon.

Resolution

These suggestions are specific to pure InstallScript project type:
Release Wizard
  • Using the General Options panel select the checkbox Create a single file executable.
  • Enter the fully qualified path to the executable followed by the comma and icon index or resource ID (preceded by a minus sign).
For example: <PATH_TO_EXES_FILES>\MyExe.exe,0
Installation Design Environment (IDE)
  • Using the Installation Designer tab in the IDE navigate to the section Media.
  • Open Media > Releases and select the appropriate release.
  • Select the Setup.exe tab.
  • Find property Setup.exe Icon File.
  • Use the ellipse to navigate to the fully qualified name of the file that contains the icon.
  • Or, enter the path and name of file followed by the comma and icon index or resource ID (preceded by a minus sign).

Related Documents

General Options Panel


Additional Information

When you specify the fully qualified name of the file from which the executable file?s icon is taken at build time; if no file is specified, a default icon is used. The warning -5031 occurs when there is an improper link to the icon file.
To specify a file, type an explicit path, select and append to a path variable, or click the browse button to open the Change Icon dialog box, in which you can click the Browse button to select a file. By default, the icon with index 0 is used; to specify a different icon, either select an icon in the Change Icon dialog box or append the icon?s index or resource ID (preceded by a minus sign) to the file name.
Was this article helpful? Yes No
No ratings
Comments

Sometimes  process either leave file in use or folders open... Saving the project and restarting the system resoled this issue for me..