InstallShield 2020
The following issues have been resolved in InstallShield 2020.
|
Issue Number |
Issue Summary |
||||||
|
IOJ-2110348 |
InstallShield used to crash while building a InstallScript MSI project, if the “Preprocessor Defines” field in the Build Setting Dialog is empty. This issue has been fixed. |
||||||
|
IOJ-2109648 |
Mixed assemblies containing both native and managed components could not be extracted by InstallShield. This issue has been fixed. |
||||||
|
IOJ-2104998 |
Microsoft OLE DB Driver for SQL Server 18.2.2.0 Prerequisite Download Location for x86 and x64 was broken when prerequisites were to download from the web. The download links have been fixed in this release. |
||||||
|
IOJ-2103083 |
The Remove and Append Operation, which was available for XML File view in InstallShield 2016 was unavailable post InstallShield 2018. The operations have been added back to the XML File View. |
||||||
|
IOJ-2102367 |
Download link for Microsoft SQL Server Compact 4.0 (x64).prq was modified by Microsoft resulting in download errors while using this prerequisite in InstallShield 2019. This issue has been fixed. |
||||||
|
IOJ-2102365 |
Prerequisite for .NET Framework 4.8 was checking an incorrect Release number, which had caused problem for Windows 10 1903 and 1909 releases. This issue has been fixed. |
||||||
|
IOJ-2097648 |
InstallShield IDE crashes while deleting Text file changes and selecting custom action and sequences. This issue has been fixed. |
||||||
|
IOJ-2094029 |
Japanese Installers for InstallShield Skin Customization Kit takes a long time to respond and complete for InstallShield 2019 and earlier. This issue has been fixed. |
||||||
|
IOJ-2086897 |
InstallShield 2019 R2 and later throws Fatal Error 6419 on building a specific project with minor upgrades built using IS 2012. This issue has been fixed. |
||||||
|
IOJ-2083142 |
Prerequisite for Microsoft SQL Server 2012 Native Client 11.2.5058.0 x64 failed to download in InstallShield 2018 and 2019. This issue has been fixed. |
||||||
|
IOJ-2077466 |
Print Button would throw an error when ‘ISPreventDowngrade’ was removed from the Upgrades View in Basic MSI project. This issue has been fixed. |
||||||
|
IOJ-2073966 |
Using Set Directory Custom Action with ‘Synchronous (Ignores Exit code)’ option for 'Return Processing' would throw Error 2723 as the option was invalid for 'Return Processing' field. The option has been removed for the field. |
||||||
|
IOJ-2073184 |
Using One Brush in "Full Wizard Background" to use a single color for header, body and navigation area did not work in InstallShield 2019 R2. This issue is fixed. |
||||||
|
IOJ-1851668 |
The binaries (OpenSSL) which are used for checking updates causes vulnerabilities. The binaries (OpenSSL) are removed now. |
||||||
|
IOJ-1922740 |
Designated 64-bit InstallScript MSI project to deploy an IIS package would loop during a silent install when it runs with a user who has no admin privileges. This issue has been fixed. |
||||||
|
IOJ-1917120 IOJ-2106599 |
The web.config file of web application deployed using an installer built with InstallShield 2018 or later has Windows authentication mode entry when the Integrated Windows Authentication is set to No. Due to this, the web application would fail to start. This issue has been fixed. |
||||||
|
IOJ-1623447 |
When chained MSI packages are excluded from the build using the release flag “NoFlags”, the custom action, which is associated with installing chained packages still is:
The issue has been fixed. |
||||||
|
IOJ-2101478 |
Updated the docker command to handle spaces in the SAB version name in Knowledge Base Article “InstallShield StandAlone Build with Docker”. |