cancel
Showing results for 
Search instead for 
Did you mean: 

Custom icon for built installer executable for Windows is incorrect when building with the command-line builder not the InstallAnywhere IDE

Custom icon for built installer executable for Windows is incorrect when building with the command-line builder not the InstallAnywhere IDE

Summary

This article discusses a known issue in which the custom icon for the built installer executable for Windows is incorrect when building with the command-line builder not the InstallAnywhere IDE.

Symptoms

This article discusses a known issue in which the custom icon for the built installer executable for Windows is incorrect when building with the command-line builder, not the InstallAnywhere IDE. An example scenario when this issue would occur would be building a project, on Windows, with a custom icon for the built installer executable for Windows using the InstallAnywhere IDE. When building a different project with the command-line builder, not the InstallAnywhere IDE, the built installer executable displays the custom icon for the first project and not the second project.

For InstallAnywhere 2012, this is the installer executable icon specified under Installer UI > Look & Feel > Installer Icon. For InstallAnywhere 2013 and higher versions, this is the installer executable icon specified under Installer UI > Look & Feel Settings > Installer Icon > Executable Icon Path.

Cause

This issue is due to the executables in the:

<IA_HOME>\resource\self_extractors\windows

directory, where <IA_HOME> is the InstallAnywhere installation directory, where InstallAnywhere itself is installed. The issue occurs because those executables retain the icon from building the project in the InstallAnywhere IDE rather than the command-line builder updating the icon, which the command-line builder should but does not do.

Steps To Reproduce

Steps To Reproduce:
  1. Create a project, Project A, with the InstallAnywhere IDE.
  2. Specify a custom icon for the installer executable for Windows. For InstallAnywhere 2012, this is the installer executable icon specified under Installer UI > Look & Feel > Installer Icon. For InstallAnywhere 2013 and higher versions, this is the installer executable icon specified under Installer UI > Look & Feel Settings > Installer Icon > Executable Icon Path.
  3. Build the project with the InstallAnywhere IDE.
  4. Create another project, Project B, with the InstallAnywhere IDE.
  5. Specify a custom icon for the installer executable for Windows.
  6. Build the project with the InstallAnywhere IDE.
  7. Build Project A with the InstallAnywhere IDE.
  8. Build Project B with the command-line builder.
Expected Results:
The built installer executable for Windows for Project B should have the custom icon for Project B, not Project A.

Actual Results:
The built installer executable for Windows for Project B has the custom icon for Project A, not Project B.

Workaround

Workaround:
  1. Open Project A in the InstallAnywhere IDE.
  2. Select the custom icon for Project A for the installer executable for Windows.
  3. Save the project.
  4. Build the project.
  5. Make a copy of the <IA_HOME>\resource\self_extractors\windows directory.
  6. Open Project B in the InstallAnywhere IDE.
  7. Select the custom icon for Project B for the installer executable for Windows.
  8. Save the project.
  9. Build the project.
  10. Make a copy of the <IA_HOME>\resource\self_extractors\windows directory.
  11. Before using the command-line builder to build Project A, first overwrite the <IA_HOME>\resource\self_extractors\windows directory with the custom icons for Project A.
  12. Before using the command-line builder to build Project B, first overwrite the <IA_HOME>\resource\self_extractors\windows directory with the custom icons for Project B.

Additional Information

For more information about the command-line builder, click here and here.

This problem is a known issue being tracked under Issue# IOA-000067127
Was this article helpful? Yes No
No ratings