InstallShield 2012 Express Edition User Guide - Knowledge Base ...

Chapter 1: InstallShield 2012 Express Edition
What Was New in Earlier Versions of InstallShield Express Edition
• After Maintenance Welcome dialog
• After Maintenance Type dialog
• After Ready to Remove dialog
• After Setup Progress dialog
• After Setup Complete Success dialog
The following two sequences are still applicable to uninstallation, so they remain under the Custom
Actions During Uninstallation node: the Before System Changes sequence and the After System Changes
sequence. Any custom actions that are scheduled during these sequences are run during uninstallation,
but not during maintenance operations such as repair.
Rollback Actions, Commit Actions, and Related Settings
The Custom Actions view has a new In-Script Execution setting that lets you select which iteration of the
execute sequence—deferred, rollback, or commit—should trigger your custom action. Deferred actions
make the run-time changes to the system. Rollback actions occur if the installation encounters an error
or the end user cancels the installation before it completes; these actions are intended to undo the
changes to the system. Commit actions perform cleanup for any temporary information that is saved by
a deferred action. The In-Script Execution setting also lets you specify whether your action should be
run in the user context (using the privileges of the user running the installation) or in the system context
(with elevated privileges).
This new In-Script Execution setting is displayed in the Custom Actions view when you select a custom
action that is not sequenced to run in immediate execution mode; actions that run in immediateexecution
mode can set Windows Installer properties and check the target system, and they are always
run in the user context.
Previously in the Express edition of InstallShield, any custom actions that were scheduled for deferred
sequences of the installation were launched in deferred-execution mode in the user context.
InstallShield did not have support for rollback or commit custom actions, and it did not have support for
running custom actions in the system context.
For more information, see:
• Using Custom Actions
• Windows Installer DLL Custom Actions
• VBScript and JScript Custom Actions
• Action Execution Options
Ability to Import Visual Studio Setup and Merge Module Projects into Existing InstallShield
Projects; Improvements for the Project Converter
InstallShield now lets you import a Visual Studio setup project or a Visual Studio merge module project
(.vdproj) into an Express project (.ise). This functionality enables you to develop InstallShield
installation projects that contain the same data and settings that were in your Visual Studio project. The
wizard imports the project outputs, files, registry keys, file extensions, custom actions, target system
searches, and launch conditions from your Visual Studio project into your existing InstallShield project.
To import a Visual Studio project into an existing InstallShield project, use the new Visual Studio
Deployment Project Import Wizard in InstallShield. The wizard lets you choose whether to import or
ignore certain settings in the Visual Studio project.
8 ISE-1800-UG01 InstallShield 2012 Express Edition User Guide