• Merge Modules
• Code Signing
• User interface
• File or Resource Managment
This section describes some of the gobal application options available in Install Time™. To locate Install Time™ options select the application start menu located in the uppper left corner and select the "options" button. See Getting Started for more information on finding Install Time™ Options. Install Time™ Options are application options that assit with customizing the product to best meet with the installation author's work style. Some options (such as ICE Validation files) allows Install Time™ to find customizations and standard locations for companion files and templates.
The General settings gives the Install Time™ user the ability to customize start up actions such as checking for
recovery files which may have occur if the computer crashed or checking for updates on start up.
The General settings is where a user can:
• Set the Default project folder - the folder where installations will be saved by default
• Set the Default project template - the template used when "new" is selected
• Set the location of any ICE validation files -
files used to validate an installation for internal integrity as well as Windows Installer compliance or best practices.
• Set whether Install Time™ should use local help files. This option is not recommended unless the computer in which
Install Time™ is install is not connected to the web.
Some users may have multiple locations in which they store Merge Modules. Under the Merge Modules options, additional folders can be added to Install Time's list of folders to scan if a merge module is added to an installation. Scan paths, such as the default Merge Module folder, can be modified at any time.
Transforms have a summary information stream that can contain validation conditions and error conditions.
Transform options are default validation options applied when creating a new transform. The validation
conditions control whether the installer can apply the transform to a given installation database.
These conditions can be set as follows:
• Major MSI version matches
• Minor MSI version matches
• MSI Update version matches
• New version equals base version
• New version is greater than or equal to base version
• New version is greater than base version
• New version is less than or equal to base version
• New version less than base version
• Installation platorm matches
• Product matches
• Upgrade code matches base MSI
While the validation of the transform can be conditioned upon the values of the UpgradeCode, ProductCode, ProductVersion and ProductLanguage properties specified in the transform and those in the installation database, the transform error conditions control which errors get suppressed when the transform is applied.
The error conditions included within the transform are overridden by the error conditions specified using the following options:
• Add existing table error
• Delete missing table error
• Add existing row error
• Delete missing row error
• Update missing row error
• Codepage mismatch error
One of the larger questions facing the software industry is this: How can users trust
code that is published on the Internet? Applications that are downloaded and run locally,
on the user's computer could be modified without additional security measures. Additionally,
there is no guarantee that the code hasn't been altered while being downloaded. Code signing
is the process of digitally signing executables and scripts to confirm the software author and
guarantee that the code has not been altered or corrupted since it was signed by use of a cryptographic hash.
See Introduction to Code Signing by Microsoft
or Adding Trust to your download by Symantec for more information
regaring code signing.
Code Sign options include the command line for appling a certificate to cabs or an exe. The default command line is incomplete and must be modified with the installation author's certificate file information by completing the 'your certificate here' section of the command line. Default command line for signtool can be restored at any time by selecting "Restore Default" button.
The default values for "Manufacturer" and "platform" can be changed here. These UI labes appear in the default dialogs. Modifying these options saves human error mistakes when creating installations.
File or Resource Managment
• Scan .NET assembly details
• Include file version attribute for scanned assemblies
• Rescan file settings during saves
• Scan file details (COM, Shortcuts, services information)
• Use advertising tables
• Use Path Variables
• File path storage:
How components are created can determine the speed and reliability of and installation and repairs.
Default - Key of the component is an executable and only one executable per component. Faster installation and application heath checks as well as covers the application critical files. Use this option if non-executable files are not required for the application to run. This is default behavior and component can be modified at any time.
One component per file - Installation and helth checks are slower, however each file is check for existence before the application is launched. Use this option if non-executable files are required for the application to run. Component can be modified at any time to be eliminate unnecessary components.
See Component Rules and Publishing Products, Features, and Components for additional information.