Übersetzungen für Produktinformationen, die noch nicht von uns übersetzt wurden, stehen über Links zu "Google Übersetzer" zur Verfügung. Bitte beachten Sie, daß automatisierte Übersetzungen nicht immer vollkommen korrekt sind.

Powered by

InstallShield Premier 2016 SP2

May 01, 2017

Updates in 2016 SP2

Funktionen

  • Integration with FlexNet Code Aware - InstallShield now includes 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.

Fehlerkorrekturen

  • When outputting the CMDLINE variable, the following value will no longer be included: -IS_temp -IS_OriginalLauncher:<path_to_setup.exe>. Where <path_to_setup.exe> will resolve to the full path to the setup launcher. This behavior was caused by a fix for a bootstrapper issue and was introduced in InstallShield 2016 SP1 (File version: 23.0.0.406).
  • Setup.exe files created by InstallScript MSI or Basic MSI projects now include support for the /clone_wait parameter so that the original setup waits for the cloned setup process to complete before exiting. Previously, when a setup.exe was created by InstallScript MSI or Basic MSI project and then added to a suite project, the suite package invoked a dialog box with the following message as a result of child processes not completing: The installation of setup appears to have failed. Do you want to continue the installation?
  • Setup.exe files created by InstallScript and InstallScript MSI projects now attempt to load DLL named _isuser_0x0000.dll from a SUPPORTDIR directory. Previously, if the language-specific file was not found first, the setup.exe would wind up looking for the language neutral file in the current working directory which was usually the path of the original launching EXE.
  • InstallShield's signing feature now includes support for SHA-1 RFC 3161 timestamp servers. Previously, InstallShield was unable to timestamp signed files with any SHA-1 RFC 3161 timestamp server.
  • InstallScript Debugger now shows breakpoints and the next statement cursor for a .rul file that is referenced by a relative path in a folder outside of the Script Files folder. Previously, when inserting or importing an additional InstallScript .rul file in a location other than the default Script Files folder and including the file using a relative path, the InstallScript Debugger ran into display issues.
  • Using Transform projects, you can now use right-click context menu options Undo Differences or Undo Differences for Entire Row in the Direct Editor. The menus options were accidentally removed from InstallShield 2009.
  • Migrating to InstallShield 2016 no longer changes the behavior of the Back push button control on the ReadyToInstall dialog. Previously, a NewDialog event with a condition of "NOT Installed AND _IsSetupTypeMin <> "Custom"" was changed to show the InstallWelcome dialog when the event was configured to show a dialog other than the SetupType dialog.
  • When a field is changed in a transform project, the changed fields are highlighted in green in the respective Direct Editor tables. Starting with InstallShield 2015 SP1, changed fields were no longer being highlighted in green as expected.
  • PowerShell custom actions are now executing when a PowerShell script file is installed with the product. Previously, PowerShell custom actions that were configured to use a script installed with the product were not able to locate the script file on the target system.
  • The Browse for Folder dialog in the InstallScript Debugger now displays a Folder edit field that lets you enter the path to a missing rul/h/InstallScript file. Previously, this dialog box provided a selection list only.
  • In a Basic MSI project and InstallScript MSI project, you can now set the Display Icon (in the General Information view) to an .ico file contained in a folder path that contains a comma. Previously, the path containing a comma was not being handled correctly, resulting, in build error -3204 ("Cannot extract icon with specified index from the file specified for the icon").
  • The InstallShield .NET dependency scanner can now locate .exe dependencies. Previously, InstallShield was able to locate only .dll dependencies.
  • Outputs containing percent symbols (%) from SQL PRINT statements are now written to a Windows Installer log correctly. Previously, InstallShield did not write the output or write truncated output only before the first percent symbol into the log.
  • InstallShield no longer crashes when building an InstallScript project containing both Microsoft Jet Database Engine 3.51 and Microsoft Jet Database Engine 4.0 merge modules.
  • Installations created by Advanced UI and Suite/Advanced UI projects now write error codes to a verbose log, allowing you to check a suite exit code based on whether a suite install failed an exit condition or not. Previously, the actual error code was not being written to the verbose log.
  • Installations created by Advanced UI and Suite/Advanced UI projects can now run EXE actions that launch a program in a SETUPSUPPORTDIR directory. Previously, the suite actions returned error 0x80070002. This behavior was caused by a fix for a bootstrapper issue and was introduced in InstallShield 2016 SP1 (File version: 23.0.0.406).
  • Setup.exe files created by InstallScript MSI or Basic MSI projects now resume on reboot even if the setup.exe name contains spaces. Previously, extra double quotes were being written to the RunOnce registry value key, which in turn prevented the install from resuming after reboot. This behavior was caused by a fix for a bootstrapper issue and was introduced in InstallShield 2016 SP1 (File version: 23.0.0.406).
  • Using the /clone_wait parameter and /L language parameter with a Basic MSI or InstallScript MSI setup.exe now works as expected. Previously, using this combination of command line parameters with a Basic MSI or InstallScript MSI was resulting in unexpected results with respect to what language was being displayed.
  • Uncompressed setup.exe files created by InstallScript MSI or Basic MSI projects can now be launched from the command line using a relative path. Previously, this resulted in unexpected behavior such as an inability to read the setup initialization file. This behavior was caused by a fix for a bootstrapper issue and was introduced in InstallShield 2016 SP1 (File version: 23.0.0.406).
  • Holding down the down arrow key to scroll in the Control Table of the Direct Editor no longer results in the IDE crashing.