Released: Sep 1, 2015

Updates in this release

Updates in 2015 SP1

• Support for Windows 10
• InstallShield includes support for Visual Studio 2015. You can create InstallShield projects from within this version of Visual Studio.
• The Microsoft App-V Assistant in InstallShield includes support for creating virtual applications that can run on Microsoft App-V 5.1 clients.
• InstallShield includes a new InstallShield prerequisite that can be used when including a Setup.exe for a generated App-V 5.x package. Note that a Setup.exe setup launcher is required if the InstallShield prerequisite needs to be included in the release.
• Windows 10 added to Operating System Options in App-V Assistant for App-V 5.x versions
• InstallShield includes new InstallShield prerequisites that you can add to Advanced UI, Basic MSI, InstallScript, InstallScript MSI, and Suite/Advanced UI projects:
  • Microsoft Visual C++ 2015 Redistributable Package (x86)
  • Microsoft Visual C++ 2015 Redistributable Package (x64)
  • Microsoft .NET Framework 4.6 Full
  • Microsoft .NET Framework 4.6 Web
• A new constant is available for the nInfoType parameter of the InstallScript function DialogSetInfo: DLG_INFO_ALTIMAGE_HIDPI. This constant specifies a high DPI image to be displayed in the dialog. High DPI image types supported include BMP, GIF, JPEG, PNG, and TIFF. If transparency is required, image types that support transparency (such as PNG) should be used and szInfoString should specify the name of the image to be displayed (optionally including the path) in the dialog. This parameter applies to all dialogs that display the standard installation image on the left side of the dialog.
• The None option has been added to the Architecture Validation options in the Releases explorer to specify the bypassing of build-time architecture validation.
• When using release flags to exclude a feature from a release, builds now complete successfully without error.
• The Japanese version of the InstallShield Files View tab (in the Options dialog) has been fixed to display properly.
• The repair function of InstallShield 2014 repairs successfully when InstallShield 2014 and InstallShield 2015 are installed on the same machine.
• Adding Primary Output in the Files and Folders view will now correctly associate components to a feature. Building the project results in the Primary Output files being included and the component added for Primary Output is associated to a feature.
• InstallShield has been updated to allow for the cloning of PowerShell custom actions.
• If you add multiple PowerShell custom actions, each PowerShell custom action now runs for each of its unique scheduled PowerShell custom action.
• Registry permission changes under HKEY_CURRENT_USER now succeed even with Windows Update KB3072630 installed.
• Typically the target version in an OSD file is automatically determined during conversion to App-V 4.x package format. The version of the shortcut target file is used, or if the target file does not have a version, then a default value of ‘1.0’ is used.
• When creating a project and including the Microsoft ReportViewer 2012 prerequisite, the Microsoft ReportViewer 2012 prerequisite files are able to download successfully without any error.
• If you attempt to save a project with a corrupt .isproj file, the corrupt .isproj file is backed up as an .isproj.bak file in the same folder, and then replaced with a fresh .isproj file.
• Deleting a registry set from an InstallScript project successfully deletes the registry.
• If you add multiple DLL files or an .exe file to the "Destination computer's files" pane of the Files and Folders view and then modify the files so that the timestamp changes in Windows File Explorer, the timestamp is now accurately updated to reflect the most recent timestamp reflected in Windows File Explorer.
• You can change the property in a SetProperty tied to a control event without error even if there are multiple events that uses the same property.
• InstallShield successfully opens the Files and Folders view when integrated with Visual Studio. Previously some projects would hang or crash when opening this view.
• InstallScript Language Support for Windows 10 documentation changes have been added to the InstallShield Help Library. The following sections have been updated: the "SYSINFO" section, the "FeatureFilterOS" section, and "ISOSL_WIN10" has been added to the "Predefined Constants" section.
• When building a project containing a .NET 2.0 assembly from MSBuild, build errors -6212 or -7325 no longer occur.
• The paths to source files are once again included in InstallScript build reports.
• For users of concurrent licenses, Server.ini now contains the proper server value after upgrading the InstallShield Standalone Build original release to the service pack release.
• The ReportViewer 2012 prerequisite in InstallShield 2015 has an updated dependency of: Microsoft SQL Server 2012 Express SP2 System CLR Types (x86).prq, which is now included in InstallShield. When you select ReportViewer 2012, the download will now succeed as a result of it successfully finding the dependent .prq.
• If you build a setup that includes a .NET Installer Class on a machine with Microsoft .NET 4.6, the Installer Class can now install correctly.