Command line options for building an .MSI from a .WSI with Wise for Windows Installer

book

Article ID: 179966

calendar_today

Updated On:

Products

Symantec Products

Issue/Introduction

 

Resolution

Question
What are the command line options I can use to build a .WSI into an .MSI?

Answer

You can invoke Wise for Windows Installer (WfWI.exe) with command line options and pass it the name of your project file (.WSI) as a parameter. WFWI.exe command lines let you compile an installation while setting options that have to do with the compile. You can also set the default value of Windows Installer properties within the installation.

You can also launch Wise for Windows Installer (WfWI.exe) in the Visual MSIDiff mode using the following command line: WFWI.EXE <base file> <compare file>. For information on Visual MSIDiff, see Comparing Windows Installer Files in the Help topics

Do not confuse this list of command line options with the command line options that you can apply at runtime to an .MSI via the executable msiexec.exe. For a list of those command line options, see Command Line Options in the Windows Installer SDK Help. You can use the Command Line page to build command lines to apply to your .MSI. See Creating a Command Line To Apply to an Installation in the Help topics.

Command line options

Description

/c

Compile only and exit. This must be the first option in the command line statement.

/releases=<release name 1>, <release name 2>

(Visual Studio only.) Compile only the specified releases from an installation containing multiple releases.

/c="release name"

Compile only the specified release from an installation containing multiple releases. (Not available in the Visual Studio integrated editor.)

/p name=value

Set property values. The property name and value must immediately follow the /p. You can use as many property name and value switches as you like in a command line. Do not enter any spaces in the name=value construction, unless they are enclosed in double quotes.

/o path

Specifies the compiled output file. You cannot specify a relative path; specify an absolute path. The path must immediately follow the /o.

/F

Has the same effect as clearing the Don't update or recompress files when saving check box on the Product Details Page

/s

Causes the compile to be silent. If you don't include this, error or informational dialogs might appear that require user intervention. (Not available in the Visual Studio integrated editor.)

/l log file name

The /l followed by a log file name makes an additional compile log file, in addition to compile.log, which is created automatically.



For further information regarding command line options for Wise for Windows Installer, see the "Command Line Options For WFWI.exe" Wise for Windows Installer help topic.