Windows Installer Editor Reference
125
Assembling an Installation
Source Pathname
The full path of the file on your computer. If this is blank, or if it is just a file
name with no path, you might be working in an .MSI, which encapsulates the
file itself.
Font Name
(File Details dialog box only.) The name of the font contained in the file, if it is a
font file.
Read Only
Make the file read-only on the destination computer.
Hidden
Make the file hidden on the destination computer.
System
Designate this file as a system file on the destination computer.
Vital
Mark this if this file must be installed correctly for the installation to succeed. If
the file cannot be installed for any reason, the installation fails.
Add to Hash Table
(Not available for multiple files.)
If this is an unversioned file, mark this to create an entry for this file in the
MsiFileHash table. Windows Installer version 2.0 or later uses file hashing to
detect and eliminate unnecessary file copying during reinstalls and repairs. It
does this by comparing a file hash stored in the MsiFileHash table to a hash of
an existing file on the destination computer. See MsiFileHash Table in the
Windows Installer SDK Help.
File has Valid Checksum
Many executable files (examples: .EXE, .OCX, .DLL, etc.) store a checksum that
can be checked against actual file contents to ensure the file is not corrupted.
Mark this to have file contents verified during reinstall or repair. If the
verification fails, the file is assumed to be corrupted and is replaced. For files
that contain checksum information, this check box is marked automatically
when you add the file to the installation.
Self-Register OCX/DLL
(Multiple Files dialog box only.) Many files support self-registration (examples:
many .OCXs and some .DLLs). Mark this to self-register these files during the
installation with an unordered registration method.
Duplicate Files
This appears only if this file was added to the installation more than once. The
duplicates are listed here for informational purposes only.
You can view and edit duplicate file entries on the Components and Features
tabs in Setup Editor.
See
Creating Duplicate File Entries
on page 371.
4. Click OK.
Note
With .NET assemblies, if you add the same file to the application directory and the
Global Assembly Cache, a duplicate file is not created because they are treated as
separate components.