InstallShield 2019 Express Edition
New Features
InstallShield includes the following new features.
New InstallShield Prerequisites for Internet Explorer 9, SQL Server 2008 R2 Native Client, Windows Identity Foundation, and Other Redistributables
InstallShield includes several new InstallShield prerequisites that you can add to projects:
| • | Internet Explorer 9 |
| • | Microsoft SQL Server 2008 R2 Native Client 10.50.1600.1 |
| • | Windows Identity Foundation |
| • | Microsoft VSTO 2010 Runtime (x64) |
| • | Microsoft Office 2010 PIA (This prerequisite installs the Microsoft Office 2010 Primary Interop Assemblies. To use this prerequisite, download the PrimaryInteropAssembly.exe file from Microsoft's Web site and run it to extract the .msi file.) |
Improvements for COM Extraction
InstallShield supports a new monitoring method for COM extraction. If you are using InstallShield on a Windows Vista or later system, this new method is used by default. The method uses a kernel driver to monitor the areas of the registry that are modified during dynamic COM extraction at build time and static COM extraction at design time. It combines the advantages that the earlier methods provided, allowing the DLL to read existing registries entries and preventing changes to the build machine.
If necessary, you can switch between the three different COM extraction methods by setting the value data of the UseAPIRegistryHooks registry value, which is in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield\RegSpy (on 32-bit machines) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InstallShield\RegSpy (on 64-bit machines). Possible REG_DWORD value data are:
| • | 0—Use API hooking to read existing registry entries for the DLL. |
| • | 1—Use registry redirection to prevent making changes to the registered DLLs on the build machine. If the value is not set, this is the default behavior on Windows XP and Windows Server 2003 systems. |
| • | 2—Use the new kernel mode monitoring, which combines the advantages of both of the other methods. If the value is not set, this is the default behavior on Windows Vista and later systems. |
Predefined System Searches for Adobe Reader 10, Internet Explorer 9, and Microsoft Office
InstallShield has new predefined system searches:
| • | Adobe Reader 10 |
| • | Internet Explorer 9 |
| • | Microsoft Office 2010 |
| • | Microsoft Office 2007 |
| • | Microsoft Office 2003 |
If your installation requires one or more of these, you can use the Requirements view or the Installation Requirements page in the Project Assistant to add these system searches 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.
Support for Software Identification Tagging
ISO/IEC 19770-2 is an international standard for the creation of software identification tags. A software identification tag is an XML-based file that contains descriptive information about the software, such as the product name, product edition, product version, and publisher. Software asset management tools collect the data in the tags to provide accurate application identification for software that is installed in an enterprise.
Software identification tagging is evolving as an industry standard, enabling independent software vendors to create smarter applications that give their customers better information for software asset management and license optimization initiatives. Including the identification tag in your product’s installation makes it possible for your customers to use tools that can monitor their internal usage of your product, allowing them to manage and optimize the number of licenses of your product that they obtain from you, and stay in compliance with your licensing policies.
InstallShield includes several new settings in the General Information view that let you specify information that is required to create an identification tag for your product. This view also contains a new Use Software Identification Tag setting that lets you specify whether you want InstallShield to create the tag at build time and include it in your installation; the default value of this setting is Yes.
Note that if Yes is selected for the Use Software Identification Tag setting but you have not entered values in one or more of the required identification settings (the Unique ID, Tag Creator, and Tag Creator ID settings in the General Information view), build warning -7235 occurs, once for each of the settings that are blank. This build warning explains that the software identification tag could not be created and included in the installation because a specific required setting was left blank. To resolve this warning, enter appropriate value in each specific setting, or select No for the Use Software Identification Tag setting.
This feature applies to Express projects.
For more information, see:
| • | Including a Software Identification Tag for Your Product |
| • | General Information Settings |
See Also
Upgrading Projects from InstallShield 2011 Express Edition or Earlier
Upgrading from Earlier Versions of InstallShield
InstallShield 2019 Express Edition Help LibraryApril 2019 |
Copyright Information | Flexera |