InstallShield 2016 » Release Wizard
The Release Wizard includes the Digital Signature Options panel if you enter digital signature information on the Digital Signature panel.
Use the Digital Signature Options panel to specify which files in your installation should be digitally signed at build time.
Tip • You can also configure digital signature information for a release on the Signing tab in the Releases view.
Setting |
Project Type |
Description |
||||||||||||
Sign Windows Installer Package |
Basic MSI, InstallScript MSI, Merge Module |
If you want to sign your Windows Installer package (.msi file), select this check box. Note • You can sign the Windows Installer package only if version 2.0 or later is selected for the MSI Engine Version setting on the Setup.exe tab. |
||||||||||||
Sign Media |
InstallScript |
If you want to digitally sign the media header file (Data1.hdr), select this check box. |
||||||||||||
Sign Setup.exe |
Basic MSI, InstallScript, InstallScript MSI |
If you want to sign your Setup.exe file, select this check box. This setting is applicable only to releases that meet the following criteria:
|
||||||||||||
Sign files in package |
Basic MSI, InstallScript, InstallScript MSI, InstallScript Object, Merge Module |
If you want to sign any of the files in your release, select this check box and then use the Include patterns and files and Exclude patterns and files boxes to indicate which files should be signed. Windows Logo Guideline • All executable files (including .exe, .dll, .ocx, .sys, .cpl, .drv, and .scr files) in an installation must be digitally signed for the Windows logo program. |
||||||||||||
Include patterns and files |
Basic MSI, InstallScript, InstallScript MSI, InstallScript Object, Merge Module |
Specify the files and file patterns that you want to be digitally signed at build time. Note the following guidelines:
For example, if you want to sign all .exe files, specify the following: *.exe Using wild-card characters is especially helpful if you include dynamically linked files in your project and you want to sign all files that match a certain pattern.
|
||||||||||||
Exclude patterns and files |
Basic MSI, InstallScript, InstallScript MSI, InstallScript Object, Merge Module |
Specify any files and file patterns that you do not want to be digitally signed at build time. Note the following guidelines:
For example, if you do not want to sign any .drv files, specify the following: *.drv Using wild-card characters is especially helpful if you include dynamically linked files in your project and you want to avoid signing any files that match a certain pattern.
|
||||||||||||
Sign files that are already signed |
Basic MSI, InstallScript, InstallScript MSI, InstallScript Object, Merge Module |
If any of the files in your project are already digitally signed, determine whether you want InstallShield to replace those existing digital signatures with the digital signature that you specify on the Digital Signature panel. Note that this affects only files that meet the requirements that are specified in the Include patterns and files and Exclude patterns and files boxes.
This check box is cleared by default. |
||||||||||||
Sign files in their original location |
Basic MSI, InstallScript, InstallScript MSI, InstallScript Object, Merge Module |
Determine whether you want InstallShield to sign your original files or just the files that are built into the release:
This check box is cleared by default. Tip • The benefit of selecting this check box for a Basic MSI or InstallScript MSI project is that it helps create one patch that updates both compressed and uncompressed versions of a release that contains originally unsigned files. |
See Also
Digitally Signing a Release and Its Files at Build Time
Digitally Signing a Release After It Has Been Built From the Command Line
Changing the Timestamp Server for Digital Signatures
InstallShield 2016 Help LibraryAugust 2016 |
Copyright Information | Flexera Software |