InstallShield 2019 Express Edition
New Features
InstallShield includes the following new features.
New InstallShield Prerequisites for .NET Framework 3.5 SP1, Microsoft Visual C++ 2012, and SQL Server 2008 R2 Express SP2
InstallShield includes the following InstallShield prerequisites that you can add to projects:
| • | Microsoft .NET Framework 3.5 SP1 (Windows Feature) |
| • | Microsoft SQL Server 2008 R2 Express SP2 (x64) |
| • | Microsoft SQL Server 2008 R2 Express SP2 (x86 & x64Wow) |
| • | Microsoft SQL Server 2008 R2 Express SP2 (x86) |
| • | Microsoft Visual C++ 2012 Update 1 Redistributable Package (x64) |
| • | Microsoft Visual C++ 2012 Update 1 Redistributable Package (x86) |
These prerequisites install the various technologies on supported target systems.
Ability to Install and Start Windows Services
InstallShield now includes support for installing a service during installation, and removing the service during uninstallation. It also now has support for optionally starting the service after installing it, starting it automatically every time that the system starts, or starting it on demand (when the service is requested through the Service Control Manager).
To configure information about a service in your project, use the new Services view.
To learn more, see the following:
| • | Installing and Configuring Windows Services |
| • | Services View |
Ability to Create Installations that Install to 64-Bit Locations
Microsoft designed 64-bit versions of Windows to allow existing 32-bit applications to continue to work seamlessly. They also designed 64-bit versions of Windows in such a way to allow a recompiled version of the same code to work seamlessly as a 64-bit application. To provide this support, 64-bit versions of Windows isolate the 32-bit and 64-bit portions from each other in two main ways: their files are stored in separate locations (for example: Program Files vs. Program Files (x86); System32 vs. SysWow64), and their registry keys are separated (HKLM\Software vs. HKLM\Software\Wow6432Node). Thus, if end users try to run a 32-bit Windows Installer–based installation on a 64-bit system, the files, folders, and registry entries that are configured to be installed to locations such as Program Files, System32, and HKLM\Software are redirected to Program Files (x86), SysWow64, HKLM\Software\Wow6432Node, respectively.
The Express edition of InstallShield now has support for creating 64-bit packages that can target 64-bit systems and install to 64-bit locations—for example, Program Files instead of Program Files (x86), System32 instead of SysWow64, and HKLM\Software instead of HKLM\Software\Wow6432Node. Previously, this support was available only in the Premier and Professional editions of InstallShield.
To enable this 64-bit support, the following changes have been made in the Express edition of InstallShield:
| • | The Files view now contains predefined folders for 64-bit locations. To specify that a file or folder should be installed to a 64-bit folder, add the file or folder to the appropriate predefined 64-bit folder. For example, to install a folder to the 64-bit Program Files Folder on 64-bit systems, add the folder to the new [ProgramFiles64Folder] node in this view. Note that 64-bit folders are not displayed by default. To display a 64-bit folder in this view: Right-click a folder in the Destination computer’s folders pane, point to Show Predefined Folders, and then click [ProgramFiles64Folder]. |
| • | The Registry view now has support for 64-bit registry locations. The SOFTWARE registry entry in the Destination computer’s Registry view pane in this view has been split into two separate nodes: SOFTWARE (32-Bit) and SOFTWARE (64-Bit). To specify that a registry entry should be installed to a 64-bit location, add the entry to the SOFTWARE (64-Bit) node, or a subnode. |
At build time, if any of the files, folders, or registry entries in the project are configured to be installed to a 64-bit location, InstallShield builds a 64-bit (x64) .msi package, which can install to 64-bit locations on 64-bit systems.
Note that a 64-bit Windows Installer–based installation can install to 64-bit locations only on 64-bit systems; they cannot be run on 32-bit systems. Note also that a 32-bit Windows Installer–based installation can be run on 64-bit systems, but it cannot install to 64-bit locations. If your product targets both 32-bit systems and 64-bit systems, you can use the Express edition of InstallShield to create one project that targets 32-bit systems, and a separate project that targets 64-bit systems.
For more information, see:
| • | Challenges of Supporting Both 32-Bit and 64-Bit Target Operating Systems |
| • | Adding Files and Folders to a Project |
| • | Displaying Predefined Folders in the Files View |
| • | Editing the Registry |
| • | Destination Folders |
Support for Preventing a Shortcut from Being Pinned to the Windows 8 Start Screen
InstallShield lets you specify whether you want each shortcut in your installation to be pinned by default to the Start screen on Windows 8 target systems. You may want to disable pinning for shortcuts that are for tools and secondary products that are part of your installation. If you disable pinning for a shortcut, the shortcut is still available in the Apps list that contains shortcuts to all of the applications on the system.
To prevent Start Screen pinning for a shortcut, use the new Pin to Windows 8 Start Screen setting for a shortcut in the Shortcuts/Folders view.
To learn more, see Shortcuts/Folders View.
See Also
Upgrading Projects from InstallShield 2012 Spring Express Edition or Earlier
Upgrading from Earlier Versions of InstallShield
What’s New in InstallShield 2013 SP1 Express Edition
InstallShield 2019 Express Edition Help LibraryApril 2019 |
Copyright Information | Flexera |