InstallShield 2019 Express Edition
New Features
InstallShield 2010 Express Edition includes the following new features.
Ability to Target Windows 7 and Windows Server 2008 R2 Systems
InstallShield enables you to specify that your installation requires Windows 7 or Windows Server 2008 R2. It also lets you build feature and custom action conditions for these operating systems.
Windows 7 and Windows Server 2008 R2 Support for Displaying Installation Progress on the Taskbar
Installations that are run on Windows 7 and Windows Server 2008 R2 now show a progress bar on the Windows taskbar during file transfer. This applies to installations that display billboards that were configured in the Billboards view. Note that a progress bar is not displayed on the taskbar on earlier versions of Windows. It is also not displayed during setup initialization or while InstallShield prerequisites are being installed.
Beta Windows Installer 5 Support for Per-User Installations
The Show All Users Option setting in the Dialogs view now has support for the MSIINSTALLPERUSER property that is available with the beta of Windows Installer 5. Use this setting to specify whether you want to give end users the option of installing your product for all users or for only the current user. Depending on the value that you select for this setting, the Ready to Install dialog may include buttons that let end users specify how they want to install the product; the buttons are displayed if the installation is run on a system that has Windows 7 or Windows Server 2008 R2.
Note that the Show All Users Option setting is now available when you select the main Dialogs node in the Dialogs view. Previously, this setting was available if you selected the Customer Information dialog in this view.
This feature is available in Express projects.
For detailed information, see:
| • | Per-User vs. Per-Machine Installations |
| • | Global Dialog Settings for All End-User Dialogs |
Beta Windows Installer 5 Support for Reducing the Time for Installing Large Packages
Use the new Fast Install setting in the General Information view to select one or more options that may help reduce the time that is required to install a large Windows Installer package. For example, you can specify that you do not want a system restore point to be saved for your installation. You can also specify that you want the installation to perform file costing, but not any other costing.
This setting configures the new Windows Installer property MSIFASTINSTALL, which can be set at the command line. Windows Installer 5 includes support for this property. Earlier versions of Windows Installer ignore it.
This setting is available in Express projects.
To learn more, see the description of the Fast Install setting.
New Support for Setting Permissions for Files, Folders, and Registry Keys
InstallShield offers a new way to secure files, folders, and registry keys for end users who run your product in a locked-down environment: With the new custom InstallShield handling method, InstallShield stores permission information for your product in the custom ISLockPermissions table of the .msi database. InstallShield also adds custom actions to your project to set the permissions. This support is available in Express projects.
Previously, the only option that InstallShield offered for setting permissions was to use the traditional Windows Installer handling. With this option, the permission information is stored in the LockPermissions table of the .msi database. The new custom InstallShield handling option offers several advantages over the traditional Windows Installer handling:
| • | The custom option includes support for many well-known security identifiers (SIDs) that are not supported by the traditional Windows Installer handling option. |
| • | The custom option supports the use of localized user names for the supported SIDs, unlike the traditional option. With the traditional option, if you try to use a localized name to set permissions on a non-English system, the installation may fail. |
| • | The custom option lets you specify that you want to deny a user or group from having the permissions that you are specifying. The traditional handling does not allow you to do this. |
| • | The custom option lets you add permissions to a file, folder, or registry key that already exists on the target system, without deleting any existing permissions for that object. With the traditional handling, the existing permissions are deleted. |
| • | The custom option lets you configure permissions for a folder (or a registry key), and indicate whether you want the permissions to be applied to all of the folder’s subfolders and files (or the registry key’s subkeys). With the traditional handling, if you want to configure permissions for a subfolder or a file in a folder (or a subkey under a registry key), the parent that is created on the target system automatically inherits the permissions of its child. |
| • | The custom option lets you configure permissions for a new user that is being created during the installation. The traditional handling does not allow you to do this; the user must already exist on the target system at run time. |
The General Information view has a new Locked-Down Permissions setting that lets you specify whether you want to use the new custom InstallShield handling or the traditional Windows Installer handling for all new permissions that you set for files, folders, and registry keys in your project. If you have already configured some permissions in your project and then you change the value of this setting, InstallShield lets you specify whether you want to use the alternate handling method for those already-existing permissions. In all new projects, the default value for this setting is the custom InstallShield handling option. If you upgrade a project from InstallShield 2009 Express Edition or earlier to InstallShield 2010 Express Edition, the traditional Windows Installer handling option is the default value of this setting. This new setting is available in Express projects.
For more information, see the following:
| • | Securing Files, Folders, and Registry Keys in a Locked-Down Environment |
| • | Selecting the Locked-Down Permissions Type for a Project |
New InstallShield Prerequisites for Windows Installer, .NET Framework, Crystal Reports, and Other Redistributables
InstallShield includes a number of new InstallShield prerequisites that you can add to Express projects:
| • | Windows Installer 4.5 (The InstallShield prerequisites for Windows Installer 4.5 include the fix that is described in Microsoft KB958655.) |
| • | Windows Installer 4.5 Update (The InstallShield prerequisites for the Windows Installer 4.5 Update include the fix that is described in Microsoft KB958655. Windows Installer 4.5 must already be installed on the target system for this update.) |
| • | Windows Installer 3.1, Windows Installer 3.0, and Windows Installer 2.0 (These versions of Windows Installer redistributables were previously available if you added Windows Installer to your project in the Releases view. These versions were not previously available as InstallShield prerequisites.) |
| • | .NET Framework 3.0 SP1 |
| • | .NET Framework 2.0 SP2 |
| • | Internet Explorer 8 |
| • | Microsoft SQL Server 2008 Express SP1 |
| • | Microsoft SQL Server 2005 Express SP3 |
| • | Microsoft Visual C++ 2005 SP1 Redistributable Package |
| • | Crystal Reports Basic for Visual Studio 2008 (Use this prerequisite with the Crystal Reports Basic installation that is installed with Visual Studio 2008. Note that you may need to change the path of the Crystal Reports Basic installation in the .prq file, depending on where the .msi package is located on your system.) |
Ability to Add IIS Web Applications to Web Sites Without Virtual Directories
InstallShield now lets you add IIS Web applications to Web sites. You can do so by right-clicking a Web site in the Internet Information Services view and clicking New Application. Once you have added a new application, you can configure its settings in the right pane.
InstallShield also lets you create a virtual directory without an application. Previously whenever you created a virtual directory, an application was also created automatically.
This feature applies to Express projects.
To learn more, see:
| • | Creating a Web Site and Adding an Application or a Virtual Directory |
| • | Internet Information Services View |
New FlexNet Connect 11.6 Redistributables Available
InstallShield includes support for FlexNet Connect 11.6 in Express projects. Use the Update Notifications view in InstallShield to include one of the two FlexNet Connect 11.6 merge modules—one has the Common Software Manager, and the other does not. These merge modules replace the FlexNet Connect 11 merge modules.
Enhancements
InstallShield 2010 Express Edition includes the following enhancements.
Usability Enhancements
Some of the views in InstallShield have been enhanced to improve productivity and usability. For example, several views contain new toolbars that make options easier to find. Some of the views that contain grids let you customize how the rows in a grid are organized. Searches are performed more quickly in the views that offer search capabilities. Following are examples of some of the highlights:
| • | Redistributables view—The new toolbar and the new group box area in this view provide robust search and organizational functionality. You can drag and drop column headings onto the group box area to organize the list of redistributables in a hierarchical format. In addition, you can type a string in the toolbar’s search box, and InstallShield hides all of the redistributables that do not contain it. |
| • | Internet Information Services view—This view has been redesigned to look similar to IIS 7: the settings are now displayed in grids, instead of on tabs. The grids have buttons that let you sort the grid settings by category or alphabetically. When you select a setting in one of the grids in this view, InstallShield displays help information for that setting in the lower-right pane. |
| • | General Information view—The settings in this view are grouped into several categories in a grid to make it easy to find a particular setting. The grid has a button that lets you sort the grid settings by category or alphabetically. |
In addition, the Output window, which is displayed when you are building a release or upgrading a project, has been enhanced. The Output window or its individual tabs can be docked to any side of the workspace in InstallShield, or they can be dragged to free-floating positions. If you drag the Output window or one of its tabs to the edge of the InstallShield interface, it becomes a docked window. If you drag the Output window or one of its tabs away from any of the edges of the InstallShield interface, it becomes undocked.
For more information, see:
| • | Working with the Group Box Area in Various Views |
| • | Docking or Undocking the Output Window |
Predefined System Searches for the .NET Framework and Internet Explorer 8
InstallShield has two new predefined system searches:
| • | Microsoft .NET Framework 3.5 SP1 |
| • | Internet Explorer 8 |
If your installation requires one or both 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.
This enhancement applies to Express projects.
See Also
Upgrading Projects from InstallShield 2009 Express Edition or Earlier
Upgrading from Earlier Versions of InstallShield
What Was New in Earlier Versions of InstallShield Express Edition
InstallShield 2019 Express Edition Help LibraryApril 2019 |
Copyright Information | Flexera |