InstallShield Premier 2018

January 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.
  • Specify Uninstallation Order of Packages in a Suite Project - In InstallShield 2018, you can now specify the uninstallation order of packages in a suite project using the new Uninstallation Order property on the Setup.exe tab of the Releases view.
  • Method to Run a Suite Installation with Minimum UI - In InstallShield 2018, you can now use a new command line parameter to run a suite installation in minimum UI mode, only displaying a progress panel.
  • Conditionally Set the Visibility of a Feature at Run Time - In InstallShield 2018, you can conditionally show or hide a feature based upon a property at run time using the new Condition option under the Visible property on the Features view of the Installation Designer.
  • Perform Recursive or Non-Recursive IIS Registration - Using this feature enables you to install both ASP.NET applications and ASP.NET Core applications to the same website.
  • Set Forms Authentication on Web Applications - InstallShield 2018 includes a new option to 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.
  • New Option to Control Whether to Load User Profile for an Application Pool Entity - In InstallShield 2018, there is a new Application Pool settings property on the Internet Information Services view, named Load User Profile, that controls whether to load the user profile for an application pool entity.
  • Add Kill Process and PowerShell Custom Actions to a Transform Project - In previous releases, you were unable to add a Kill Process or PowerShell custom action to a Transform project. In InstallShield 2018, you can now add a New Kill Process or New PowerShell custom action to a Transform project in the Custom Actions and Sequences view.
  • Save QuickPatch Projects in XML Format - In InstallShield 2018, you can now save a QuickPatch project in XML format, and you can also create a QuickPatch project from projects saved in XML format. In previous releases, QuickPatch projects could only be saved in binary format.
  • Localize Product Name Property in Suite Projects - In InstallShield 2018, suite projects now support localizing the Product Name property.
  • Include the Value of a Property in a Product Configuration’s Setup File Name - In InstallShield 2018, you can now include the value of a property from the Property Table in product release
  • configuration setup and package file names.
  • New MSBuild Parameters to Set Summary Information Stream Comments and to Set Package File Name - In InstallShield 2018, new MSBuild parameters were added to enable you to set add comments to an installer and to set the package file name of an installer.
  • Specify Line Break and Tab Characters in Text File Changes - In your installer, you can configure search-and-replace behavior for content in text files that you want to modify at run time on the target system. To do this, you open the System Configuration > Text File Changes view and add a text Change Set that identifies the text files that will be searched at runtime, and also specifies the text to search for (Find What) and the text to replace it with (Replace With). In InstallShield 2018, when adding a text Change Set, you can now enter escape sequence characters in the Replace What field to specify a line break or a tab.
  • Remove or Hide the Suite Loading Screen - To control whether this screen is displayed, a new property has been added to the Setup.exe tab of the Releases view named Show Suite Loading Screen. If you want to hide the Suite Loading Screen for your Advanced UI or Suite/Advanced UI setup launcher, set this property to No.
  • Setting to Always Create Debug Logs for Suite Installers - In InstallShield 2018, you can now select an option to turn on logging for a suite project without passing debuglog through the command line.
  • A new option, Always Create Debug Log, has been added to the Setup.exe tab of the Releases view for Advanced UI and Suite/Advanced UI projects.
  • New Out-of-the-Box Dialog to Set the IIS Certificate File for SSL Certificate at Runtime - InstallShield 2018 includes a new out-of-the-box dialog (IISBrowseSSLCertificate) for the installer that enables the end user to browse to a IIS certificate file that they provide for the SSL Certificate and enter a password at installation runtime.
  • Specify Absolute or Relative Path When Creating New Child Elements in an XML File - In InstallShield 2018, a new setting has been added to the XML File Changes view named Use Absolute XPath to enable you to specify that you want to use an absolute path when creating child elements.
  • Setting the Default Keyboard Focus for Dialog Box Controls in Suite Projects - In InstallShield 2018, when defining the wizard pages for a Suite project, you can now specify which control on a wizard page will have the default keyboard focus.
  • PowerShell Script Editor in Basic MSI Projects - In InstallShield 2018, the PowerShell script editor is available on the Custom Actions and Sequences > Custom
  • New Option to Open Existing Transform File in InstallShield Transform Wizard - In InstallShield 2018, you can now open an existing transform file in the InstallShield Transform Wizard (as if it
  • were being opened in the Transform Wizard for the first time), where you will be prompted to select a base MSI package for the transform file. This enables you to use the same generic transform file for multiple MSI packages.

Fixes

  • When creating a new QuickPatch project based on a previous QuickPatch project, and selecting a QuickPatch ISM that is in XML format, the Create New QuickPatch wizard displays the following error message:
  • <ProjectName>.ism is not a valid ism file. Please specify a valid QuickPatch project (.ism file) in the Existing QuickPatch Project field.
  • After using the New Language Wizard to add a new language to an InstallScript project, building with the InstallShield IDE successfully adds the new language to the media. However, performing the build on the Standalone Build System fails to add the language to the media, even after adding the new language to the Standalone Build.
  • 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.
  • The features that install JRE50 and JRE7 in the InstallShield 2016 Prerequisite installer display incorrect names and descriptions. The feature name for JRE50 is displayed as ID_STRING102 and the feature name for JRE7 is displayed as ID_STRING94. The names of the features to be installed should contain a descriptive name reflective of the files that will be installed for that feature.
  • Specifying a Wizard Lite Wizard Format for the Suite UI displays a white strip along the top of each wizard page. The title and header image appears to be removed.
  • When customer tries to use a PowerShell custom action that uses the Import-Certificate cmdlet to install a certificate into the certificate store, the script works as expected outside of InstallShield, but when used in a PowerShell custom action, this cmdlet appears to do nothing.
  • In an InstallShield 2016 project, XCopyFile throws error 0x80070020. In an InstallShield 2014 project, XCopyFile returns 0.
  • When installing the FlexNet License Server (11.13.1.5) for use with a concurrent license, if you specify different port numbers for use with the HTTP port and the License Server Manager port, the ports are not saved and are reverted back to the default ports (8090 for HTTP and 20071-79 for License Server Manager port).
  • Microsoft SQL Server 2016 Express prerequisites fail to download.
  • When using Text Replacement in the SQL Scripts view, you are unable to replace a string with the same value but different case sensitivity. For example, finding the string testvalue and replacing it with TestValue fails; the script retains the value of testvalue. This occurs with the Preserve case option unselected. This behavior would be expected if Preserve case was selected.
  • InstallShield 2016 SP1 setup.exe installer can use LAAW_OPTION_WAIT_INCL_CHILD as a parameter for the original setup to wait for the termination of the clone process.
  • The Direct Editor displays a red signature column in the RegLocator table. When a second system search is configured that uses the RegLocator table instead of the Signature table, the Signature column in the RegLocator table is red.
  • When a new shortcut is created from the Project Assistant view, InstallShield automatically generates a short file name for the newly generated shortcut. If the newly generated shortcut is renamed from the Project Assistant view, a short file name is not generated for the renamed shortcut.
  • Calling a Basic MSI setup launcher from a command prompt and including parameters where the entire command exceeds 752 characters results in a “Setup Launcher Unicode Has Stopped Working” error. Although the error is seen, the MSI still launches and does contain all of the properties passed on the command line.
  • After applying a hot fix to an older version of InstallShield, using a relative path on the command line causes the setup to fail to launch.
  • When adding a scheduled task to a merge module project and including it in a Basic MSI project, build warning -6524 occurs.
  • Opening an InstallShield 2015 SP1 Basic MSI project in a Visual Studio 2015 solution causes hang and/or problems with the Visual Studio interface. The Solution Explorer becomes unresponsive.
  • The InstallShieldPrereqs_SQLServer.exe installer installs the SQL 2016 Express prerequisites to the SQL 2014 Express location, replacing the 2014 prerequisites.
  • When an MSI file is converted to an InstallShield project, the resulting .ism file does not reflect the Always Overwrite file settings that were set in the original MSI file.
  • When a suite project is run on Windows Server 2016, an error is encountered when attempting to enable an IIS Windows feature: runtime error 0x800f080c.
  • The XCopyFile() function is unable to copy a locked file when the LOCKEDFILE constant is passed. The message “Access is denied” is displayed.
  • If the ntmarta.dll file is located in the same folder as an InstallScript single .exe installer, it will cause a Unicode crash during setup initialization.
  • 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.
  • Changing the brush color for the footer brush in a Suite project does not update the footer color for dialogs displayed in the InstallShield interface after a dialog has been viewed. However, the correct color is displayed: 1) if the user saves the project, then closes InstallShield and opens the project again, and 2) if the user changes the brush color prior to viewing a Wizard Page dialog in the IDE. The correct color is displayed at runtime; this is an interface problem.
  • A PowerShell custom action that uses the New‐SelfSignedCertificate cmdlet to create a certificate in the certificate store of the local machine does not behave as expected. The script works as expected outside of InstallShield, but when used in a Suite PowerShell custom action, the cmdlet does not create the certificate.
  • A suite installer that includes the Microsoft VC++ 2015 Update 3 prerequisite will crash on Microsoft Server 2008 if Microsoft VC++ 2015 Update 3 is already installed on the system.
  • When you include a right-to-left language and run a patch or minor upgrade (setup.exe), runtime error 2721 occurs based on binary table data.
  • InstallShield crash at build exception ACCESS VIOLATION (0xc0000005) at address <foo> trying to read address <dat>.
  • After applying an InstallShield hot fix, InstallShield MSI installers do not cache all language files, causing panels to display in the default language when launched from Add/Remove programs.
  • InstallScript MSI projects that use the new style InstallScript user interface type fail at runtime. The actual behavior varies slightly depending on if a setup launcher is included or not. In both cases the package does get installed.
  • Starting with InstallShield 2016, the Build Report Summary does not update any of the numbers for features, merge modules, prerequisites, dynamic links, or files. These all display 0. The number of components was also removed.
  • Change in InstallShield 2015 SP2 / 2016 is causing an issue with the UseDLL() function.
  • When using a differential media release for an upgrade, it can cause the “InstallShield Installation Information” folder to be missing the cached package, causing problems with repairs of missing files.
  • SETUPEXEDIR does not resolve to the expected value when passed to an InstallShield prerequisite.
  • Upgrading a Suite project from a previous version of InstallShield will remove the value from the string IDS_SUITEERROR_ABORTCONDITION.
  • Suite run using system context results in MSI parcel launch result: 80070003.
  • If the cryptbase.dll file is located in the same folder as a setup.exe installer file, it will be loaded during setup initialization.
  • 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.