09.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 16: Building, Testing, and Distributing Installations<br />

Testing and Running Installations<br />

Testing and Running Installations<br />

Before distributing your installation, you should test run it to ensure you discover any issues rather than<br />

your customers. <strong>InstallShield</strong> enables you to test the end-user dialogs (without copying any files to the<br />

target system) and run the entire installation including transferring files.<br />

Testing and Running Installations<br />

Testing your release is a necessary step in the installation development process. You can test your<br />

release in one of two ways:<br />

• Run your installation—This option executes your installation exactly as it would on an end user’s<br />

machine. All files are transferred, shortcuts and registry entries are made, and the end-user<br />

interface is displayed. Although you can run this type of test from the <strong>InstallShield</strong> interface, it is<br />

also a good idea to test your installation on several clean machines before you release it to the public.<br />

• Test your installation—When you test your installation, only the end-user interface elements are<br />

executed. No file transfer takes place and no changes to your machine occur. The only exception to<br />

this rule is if you have custom actions in your installation. All custom actions execute during this<br />

test.<br />

Task To test or run an installation:<br />

1. In the View List under Prepare for Release, click Releases.<br />

2. In the Builds explorer, click the release that you want to test or run.<br />

3. Click the Run button or the Test <strong>User</strong> Interface button on the toolbar.<br />

Running an Installation in Silent Mode<br />

If you do not want to have the Setup.exe progress bar displayed when it launches, you can use the /s<br />

command-line parameter. For example, if you enter Setup.exe /s, Setup.exe launches, but the user<br />

interface is not displayed. If you want the .msi package to run silently as well, you need to pass the /qn<br />

command-line parameter through Setup.exe using the /v parameter—for example:<br />

Setup.exe /s /v/qn<br />

Conditional Installations<br />

<strong>InstallShield</strong> provides the capability to make your installation conditional based on several criteria. This<br />

can be accomplished using the Requirements view. If the installation is run on a machine that does not<br />

meet the specified conditions, the installation exits and your application is not installed.<br />

316 ISE-1800-UG01 <strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!