InstallShield 2024 R2
The following issues have been resolved in InstallShield 2024 R2:
|
Issue Number |
Issue Summary |
|
ISDEV-44009 |
The VSSolutionFolder path variable in Visual Studio 2022 failed to update with the solution folder path and was marked as undefined in the Basic MSI project. This issue has been fixed. |
|
ISDEV-38847 |
When the Prompt Message setting on the Updates tab was enabled and no prompt message was configured, the latest version of a Suite package was installed as a Force Install and the installation proceeded without any prompt message. This issue has been fixed. |
|
ISDEV-44001 |
The VC2022 prerequisite failed to install when the InstallShield Prerequisites Location setting on the Setup.exe tab was set to Download From The Web. This issue has been fixed. |
|
ISDEV-43906 |
When the LAAW_OPTION_WAIT option was passed to the DoInstall InstallScript function, the main installer failed to wait, leading to an unexpected behavior of the subinstaller. This issue mainly arose due to the usage of the LaunchAppAndWait function in InstallScript code before the Doinstall call. This issue has been fixed. |
|
ISDEV-43756 |
A failure was observed when installing the Premier Edition of InstallShield 2023 R2 on 32-bit platforms. This issue has been fixed. |
|
ISDEV-44081 |
A suite update related pop-up dialog box appeared each time the Remind Me Later or Download option was clicked. This issue has been fixed. |
|
ISDEV-43881 |
A crash was observed in a Merge Module project when navigating to the Events tab in the Releases explorer after renaming the product configuration and release in the Releases explorer. This issue has been fixed. |
|
ISDEV-43768 |
On a Japanese version of the Windows platform, the text in the InstallScript initialization dialog box failed to appear in a single line, and instead appeared in two separate lines. This issue has been fixed for skinned dialogs. |
|
ISDEV-44048 |
Creating an InstallShield project integrated with a Visual Studio solution resulted in the failure to open the Visual Studio solution, accompanied by the appearance of the following error message: InstallShield has not been initialized. InstallShield must be run at least once by a user with Administrator or Power User privileges. This issue has been fixed. |
|
ISDEV-43720 |
Specifying a previous version of a package led the InstallShield build process to automatically and incorrectly modify the file extension of one of the four payload files for a minor upgrade. This issue has been fixed. |
|
ISDEV-44108 |
An installation delay was observed when attempting to install a Basic MSI project with InstallScript custom actions without an Internet connection. This issue has been fixed. |
|
ISDEV-44014 |
A build failure was observed when the ISSetup.dll file was digitally signed twice using the custom signing method. This issue has been fixed. |
|
ISDEV-44109 |
Installing a setup.exe file with the /clone_wait command-line parameter resulted in the addition of the -waitingforchildprocess as a command-line parameter. This issue has been fixed. |
|
ISDEV-42677 |
An InstallScript project failed to display the correct pre-version of the product while upgrading the product to the latest version. This issue has been fixed. |
|
ISDEV-43737 |
A dialog box with version update information, configured via the Enable Updates Check area on the Updates tab, failed to appear on the top of the Suite Loading Screen and was instead displayed behind it. This issue has been fixed. |
|
ISDEV-25749 |
Selecting the Slate, Midnight, or Olive dialog skin in the Skins folder of the Dialogs explorer in the User Interface view led to the improper alignment of the Print button on the License Agreement panel during an InstallScript installation. This issue has been fixed. |
|
ISDEV-43640 |
The MD5 check failure for the initial package in a Suite/Advanced UI project failed to abort the same project installation. This issue has been fixed. |
|
ISDEV-44204 |
The ISHiddenProperties property failed to prevent the password value of properties—whose names were defined by it—from being logged as plain text when utilizing these properties in the Argument setting on the Action tab of the Events view. This issue has been fixed. |
|
ISDEV-44146 |
A failure was observed for the MSIHiddenProperties property to prevent the properties value—whose names were defined by it—from being logged as plain text when utilizing these properties in the Text File Changes view. This issue has been fixed. |
|
ISDEV-43637 |
The InstallShield Wizard dialog failed to display the /a setup.exe command-line parameter during an installation. This issue has been fixed. |
|
ISDEV-43569 |
Changing the TARGETDIR property value to a customized location containing multiple languages Unicode characters led to an installation failure of the objects configured in an InstallScript project. This issue has been fixed. |
|
ISDEV-42603 |
A failure was observed when attempting to sign the Swidtag.xml file using the CNG Certificate, accompanied by the following error message: ISDEV : error -1027: Failed signing regid.2000 08.com.revenera_BDC3653D-36B2-4E2F-A7B6-9C2BF12E6278.swidtag This issue has been fixed. |