What’s New in InstallShield 2019
InstallShield includes the following new features:
| • | New Features in InstallShield 2019 R3 |
| • | New Feature in InstallShield 2019 R2 |
| • | New Feature in InstallShield 2019 |
New Features in InstallShield 2019 R3
For information about new features added in InstallShield 2019 R3, refer to the following section:
| • | Standalone Build on a Docker Container |
| • | Support for File Redirection Fixup |
| • | Use OLE DB Driver for SQL Server |
| • | Choose SQL Driver for Database Server |
| • | Ability to Configure Patch Design Patches Through the Automation Interface |
Standalone Build on a Docker Container
InstallShield Standalone Build (SAB) can now be installed and run in a Docker container.
Instructions on how to set up an InstallShield 2019 R3 Standalone Build on a Docker container or to download an already set up InstallShield 2019 R3 Standalone Build on Docker Hub can be found in the InstallShield StandAlone Build with Docker KB article.
Support for File Redirection Fixup
In the previous release, InstallShield added support for Package Support Framework with file redirection and custom fixups for MSIX.
The InstallShield 2019 R3 release includes an enhancement that permits you to customize the file redirection fixup parameter executable name. This applies to executables that launch multiple processes.
In the previous release, the redirection fixup parameter executable was given the same name as the primary process. In InstallShield 2019 R3, a new field, Executable, has been added to the Package Support Framework area of the Application Settings view of an MSIX project type to enable you to specify the redirection fixup parameter executable name. By default, this field is populated with the primary process name.
Use OLE DB Driver for SQL Server
The previous Microsoft OLE DB Provider for SQL Server (SQLOLEDB) and SQL Server Native Client OLE DB provider (SQLNCLI) remains deprecated.
Now, Microsoft has released a new OLE DB provider called Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL).
InstallShield 2019 R3 now uses Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) to support TLS 1.2 only environments.
Advanced Note:Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) is included as a prerequisite in InstallShield 2019 R3.
Choose SQL Driver for Database Server
In InstallShield 2019 R3, you can now choose a driver from a list of drivers for your database server.
By default, the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) will appear on the Requirements tab for your new SQL connection.
Ability to Configure Patch Design Patches Through the Automation Interface
In previous releases, you could not configure Patch Design patches through the automation interface; you could only build pre-created patches through automation.
In the InstallShield 2019 R3 release, you can now configure Patch Design patches through the automation interface.
New Feature in InstallShield 2019 R2
For information about new features added in InstallShield 2019 R2, refer to the following section:
| • | MSIX - Package Support Framework |
MSIX - Package Support Framework
The Package Support Framework is an opensource kit that helps you apply fixes to your existing win32 application when you don't have access to the source code, so that it can run in an MSIX container.
It helps your application follow the best practices of the modern runtime environment. It contains an executable, a runtime manager DLL, and a set of runtime fixes to a package.
When the users start your application, the Package Support Framework launcher is the first executable that runs. It reads your configuration file and injects the runtime fixes and the runtime manager DLL into the application process. The runtime manager applies the fix when it's needed by the application to run inside of an MSIX container.
In InstallShield 2019 R2, you can now use the Package Support Framework that contains runtime fixes such as the File Redirection Fixup and Custom Fixup in MSIX.
| • | File Redirection Fixup - You can use the File Redirection Fixup to redirect attempts to write or read data in a directory that isn't accessible from an application that runs in an MSIX container. |
| • | Custom Fixup - You can use the Custom redirection fixup that will solve application compatibility issues with a configuration file that specifies the fixes that you want to apply to your application. |
New Feature in InstallShield 2019
For information about new features added in InstallShield 2019, refer to the following section:
| • | Use MSIX Project Type to Build an MSIX Package |
| • | MSI to MSIX Conversion Wizard |
| • | Build MSIX Validation Suite for Basic MSI |
| • | Add MSIX in Suite |
| • | New Project Wizard |
Use MSIX Project Type to Build an MSIX Package
MSIX is the Windows app package format that provides a modern packaging experience to all Windows apps. The MSIX package format preserves the functionality of existing app packages and/or install files in addition to enabling new, modern packaging and deployment features to Win32, WPF, and WinForm apps.
In InstallShield 2019, you can now use MSIX project type to build MSIX packages. It contains windows applications for side-loading or distribution via the Windows Store.
| • | Package Information |
| • | Package Payload |
| • | Media |
Now you can describe and identify your project by providing:
| • | General Information view to specify details such as the name and format of the project file. |
| • | MSIX VisualAssets explorer to offer an integrated, visual method for describing visual aspects of the MSIX apps. |
| • | Capabilities view that requires to be enabled in app's package manifest to access certain API or resources like pictures, music, or devices such as the camera or the microphone. |
| • | Declarations view that provides a visual tool for creating and managing the application, package level declarations and allows to configure their properties. |
| • | Content URIs view to specify the URIs that can use window.external.notify to send a Script-Notify event to the app. |
Now you can specify the files that designs your MSIX application:
| • | Files and Folders view lets you to add files to your InstallShield project. You can organize these files into folders on the target system. |
| • | Applications view offers an integrated, visual method for designing windows app properties that comprises part of or all of the functionality delivered in the package. |
| • | Registry view enables you to define registry keys and values to be created by your installation. |
Now you can customize the files and folders that you will use to distribute your installation:
| • | Path Variables view makes your installation easily portable between development systems through the use of variables. |
| • | Releases view provides a visual tool for each product in your project. |
The MSI to MSIX Conversion Wizard helps you convert existing Windows Installer files (.msi files) to MSIX package through Basic MSI project.
Build MSIX Validation Suite for Basic MSI
You can now identify the existing InstallShield projects that require changes to meet the Microsoft MSIX standards. It also provides insights and steps needed to convert MSI project elements to work in MSIX.
Now in InstallShield, you can include a set of validators called the InstallShield MSIX Suitability Suite.
The InstallShield MSIX Suitability validators in this suite scan an.msi package for signs of items that are unsuitable for the MSIX package (.msix) format.
In InstallShield 2019, you can add an MSIX package in Suite and install along with other deployment package types.
The New Project Wizard helps you to select different project types with ease.
There are different tabs in the New Project Wizard which are given below:
| • | Common Project Types - Use the most commonly used project types. |
| • | InstallScript Project Types - Use the previously built projects which uses the InstallShield setup engine with InstallShield Professional |
| • | Windows Installer Project Types - Use the previously built projects which uses the Microsoft Windows Installer (MSI) setup engine with InstallShield |
| • | MSIX Project Types - Use the Windows app package format |
| • | All Project Types - Use all the available project types and any custom templates. |
InstallShield 2019 R2 Enhancements
InstallShield 2019 R2 includes the following enhancements:
| • | Delay between Signing |
| • | IsCmdBld.exe Parameter to Specify Digital Certificate Password |
| • | Allow Suite Project to use Relative Path to link to ISM Package |
| • | Update SQL 2012 Native Client prerequisites |
| • | Add Windows Server 2019 in PRQ Conditions |
InstallShield 2019 R2 supports adding a delay between the successive digital signing, this requires only if the timestamp server fails handle the successive signing requests.
Required to specify the <DelayBetweenSigning default="1500"/> node in the settings.xml, under <DevStudio/Build> node in Settings.xml in milliseconds.
Find the Settings.xml file that is installed with InstallShield. Settings.xml is installed in one of the following locations, depending on which language version of InstallShield you are using:
| • | English—InstallShield Program Files Folder\Support\0409 |
| • | Japanese—InstallShield Program Files Folder\Support\0411 |
IsCmdBld.exe Parameter to Specify Digital Certificate Password
Project:This information applies to the following project types:
| • | Basis MSI |
| • | InstallScript |
| • | InstallScript MSI |
| • | InstallScript Object |
| • | Merge Module |
| • | Suite/Advanced UI |
| • | Advanced UI |
In InstallShield 2019 R2, there is a new parameter (cert_password) that specifies the digital certificate password, this is an optional parameter in the command line build (IsCmdBld.exe).
If it is not specified, the password configured in the project is used to sign the files.
Allow Suite Project to use Relative Path to link to ISM Package
Project:This information applies to the following project types:
| • | Basis MSI |
| • | InstallScript |
In InstallShield 2019 R2, now when trying to build a modified project, you will be able to link an ISM package using a relative path.
Update SQL 2012 Native Client prerequisites
Project:This information applies to the following project types:
| • | Basis MSI |
| • | InstallScript |
| • | InstallScript MSI |
In InstallShield 2019 R2, the Microsoft SQL Server 2012 Native Client prerequisites (x86 and x64) which is now included for the latest versions of 2012 Native Client.
Add Windows Server 2019 in PRQ Conditions
Project:This information applies to the following project types:
| • | Basis MSI |
| • | InstallScript |
In InstallShield 2019 R2, you can set the Prerequisite Condition to run on a specified platform for Windows Server 2019. You can set the appropriate PRQ Conditions in the Prerequisite Editor by selecting or deselecting the option.
Enhancements in InstallShield 2019
InstallShield 2019 includes the following enhancements:
| • | View Details of a Selected Certificate |
| • | Add Windows Server 2019 for Operating System Requirement |
| • | Add Predefined Install Conditions |
| • | Update TimeStamp Server Selection for Digital Signatures |
| • | Support for Suite Projects using MSBuild |
| • | Customize Debug Log File Name |
| • | Customize Custom Return Code |
| • | Customize Setup File Name |
| • | Support for InstallShield Standalone Build |
View Details of a Selected Certificate
Project:This information applies to the following project types:
| • | Basis MSI |
| • | InstallScript |
| • | InstallScript MSI |
| • | InstallScript Object |
| • | Merge Module |
| • | Suite/Advanced UI |
| • | QuickPatch |
| • | MSIX |
In InstallShield 2019, the details of the certificate like the general information of the certificate, security details and certification path is listed on the View Details option in the Certificate Selection dialog box.
Add Windows Server 2019 for Operating System Requirement
Project:This information applies to the following project types:
| • | Basis MSI |
| • | InstallScript MSI |
In InstallShield 2019, you can add an option for Windows Server 2019 in the operating system requirements section. You can set the appropriate Install Condition in the project by selecting or deselecting the option.
Add Predefined Install Conditions
Project:This information applies to the following project types:
| • | Basis MSI |
| • | InstallScript MSI |
InstallShield has new predefined system search:
| • | Microsoft .NET Framework 4.6.2 |
If your installation requires the above, you can use the System Search view or the Installation Requirements page in the Project Assistant to add this system search to your project. When end users launch your installation, Windows Installer checks the target system to see if the requirements are met; if they are not met, the installation displays the error message that is defined for the system search.
Update TimeStamp Server Selection for Digital Signatures
Project:This information applies to the following project types:
| • | Advanced UI |
| • | Basis MSI |
| • | InstallScript |
| • | InstallScript MSI |
| • | InstallScript Object |
| • | Merge Module |
| • | Suite/Advanced UI |
In InstallShield 2019, if you select
| • | SHA-1 to sign the package, the package will get time timestamped using: |
<DigitalSignature Timestamp="http://timestamp.verisign.com/scripts/timstamp.dll"/>
| • | SHA-256 to sign the package, the package will get time timestamped using: |
<DigitalSignature TimestampRFC3161="http://sha256timestamp.ws.symantec.com/sha256/timestamp"/>
Support for Suite Projects using MSBuild
Project:This information applies to the Suite/Advanced UI projects.
InstallShield supports the Microsoft Build engine (MSBuild) included with the .NET Framework. MSBuild support enables you to build Visual Studio solutions with InstallShield projects where Visual Studio is not installed in the build lab environments.
In InstallShield 2019, you can now build suite projects (.sln) which are created in Visual Studio using MSBuild.
Project:This information applies to the Suite/Advanced UI projects.
An option, Always Create Debug Log, had been added to the Setup.exe tab of the Releases view for Advanced UI and Suite/Advanced UI projects.
Now in InstallShield 2019, you can specify the debug log file name which will be generated.
Project:This information applies to the following project types:
| • | Basic MSI |
| • | InstallScript MSI |
| • | InstallScript |
In InstallShield 2019, you can now override the return code of setup.exe with your own custom values during the runtime.
Project:This information applies to the following project types:
| • | Basic MSI |
| • | InstallScript MSI |
| • | InstallScript |
| • | Suite/Advanced UI |
In InstallShield 2019, you have the ability to customize the original file name property for setup.exe.
Support for InstallShield Standalone Build
Now when you install the InstallShield Standalone Build, the Automation Interface feature is set to default selection.
This allows you to install the Automation Interface feature without selecting manually.
Additional Prerequisites Included
InstallShield 2019 includes the following additional prerequisites:
| • | Microsoft .Net Core 2.1 Runtime Prerequisite |
Microsoft .Net Core 2.1 Runtime Prerequisite
InstallShield now includes the prerequisites for Microsoft .Net Core 2.1 Runtime in the redistributables view.