Released: Jan 19, 2018

Updates in 2018

Features

• Perform Open Source Risk Assessment with FlexNet Code Aware - InstallShield now includes full integration with FlexNet Code Aware, an automated open source risk assessment and package discovery solution that enables you to quickly scan your products for security and intellectual property (IP) compliance risk.
  • Supported File Types - FlexNet Code Aware supports analysis of the following files:
    • Java Packages.
    • Node Packages.
    • Nuget Packages.
    • RPM Packages.
    • Ruby Packages.
    • EXE and DLL Files.
• Set Forms Authentication on Web Applications - This new option, Forms Authentication, is displayed under the Authenticated Access section of the Internet Information Services view for a website.
• Include the value of a property in a product configuration’s setup file name.
• New MSBuild parameters to set summary information stream comments and to set package file names.
• Additional Prerequisites Included
  • Visual C++ 2017 x86 and x64.
  • Microsoft SQL Server 2014 SP1 and SP2.
  • Microsoft .NET Framework 4.7.

Fixes

• Dependent files are not being included in the InstallShield package when building an InstallShield project with MSBUILD. However, dependent files are included when building the same project using the Visual Studio interface.
• When you attempt to use COM extraction in InstallShield on a poorly written DLL, it will get stuck in an infinite loop during registration. InstallShield will hang indefinitely instead of stopping the process and displaying an error message after a certain amount of time has elapsed.
• Microsoft SQL Server 2016 Express prerequisites fail to download.
• If you run a Basic MSI single EXE installer, it will extract files/setup files to a GUID folder in TEMP. However when the setup is finished, it will clean up all files except for the setup installer EXE file (which will be left in the TEMP folder).
• Checking for updates in InstallShield 2016 SP2 causes Software Manager to display “The product version is not registered on the server” instead of displaying the message that no updates are available.
• SETUPEXEDIR does not resolve to the expected value when passed to an InstallShield prerequisite.
• Request that a registry convention be used as a condition for the Microsoft Visual C++ 2015 Update 3 redistributable instead of the msvcp140.dll file, which could be unreliable.