Adding a Digital Signature to an Installation
Windows Installer Editor Reference
WFWI.EXE Command Line Option Example
The following example shows how to compile an installation from the command line.
"path\WFWI.EXE" C:\Installers\MyApp.wsi /c /s /p CURRENT_FILES="E:\Test
Development" /o C:\MyAppInstaller.msi
The preceding command line does the following:
Invokes the executable
Specifies the .WSI to compile (C:\Installers\MyApp.wsi)
Sets it to compile (/c)
Sets all error messages to be suppressed (/s)
Sets the property CURRENT_FILES (/p CURRENT_FILES="E:\Test Development")
Sets the output location (/o C:\MyAppInstaller.msi)
If you set multiple properties, separate the property value pairs with spaces. Enclose the
values with double quotes.
Automating the Build Process
You can use the WFWI.exe command-line options in conjunction with other processes to
create an automated build process.
Enter the following command-line statement into a batch file or any other program that
has the ability to run command-line statements, such as Scheduled Tasks in Control
Panel:
"path\WFWI.EXE" "path\project file" /c /o "path\output file" /s
where:
"path\WfWI.exe" is the path to the Wise executable
"path\project file" is the path to the installation (.WSI) or merge module (.WSM)
project file to compile
"path\output file" is the location of the compiled installation (.MSI) or merge module
(.MSM)
Use the Digital Signature page to add an Authenticode digital signature to an installation
file so its integrity and authenticity can be verified.
Digital signature methods
The file signing tool that is used to digitally sign a file depends on the type of your digital
certificate:
Public/private key pair files
This method requires a credentials file (.SPC or .CER) and a private key file (.PVK).
This method is supported by the signcode.exe tool. For details, search for
"Signcode" in the MSDN Library (msdn.microsoft.com/library/).
Personal Information Exchange file
Advanced Installations
233