User Guide

393
Components Tab
•Key Path
Select the item Windows Installer should use as a key path. The drop-down list
shows files, registry entries, or ODBC data sources that are included in the
component, depending on your selection in the Key Path Type field. See About
the Key Path on page 394.
• Always increment shared .DLL count
Mark this to increment the count of applications using .DLLs in this component
when installing it, even if the component is already installed. If a component is
installed to the Global Assembly Cache, you cannot increment the reference
count.
• Leave installed on uninstall
Mark this to leave the component installed when its feature is uninstalled.
• Check condition during reinstall (Transitive)
Mark this to check the condition not only on the original installation but also
when the component is re-installed.
• Never overwrite if key path exists
Mark this to prevent the component from being installed if the item specified as
the key path already exists.
• 64-bit component
(64-bit installations only.) Mark this to designate the component as a 64-bit
component. The target directory and the component must both be either 32-bit
or 64-bit. If one is 32-bit and the other is 64-bit, a warning message appears,
giving you the option to change the target directory to match the component.
Example: If this checkbox is marked and the Directory is Program Files (x86),
you are prompted to change this target directory to its 64-bit counterpart,
Program Files.
• Self-register key path file before compile
Mark this so that, each time you compile, the file referenced in the Key Path
field is re-registered, the registration information is rescanned, and any new
information is added to the installation.
If you clear this checkbox, then the file is not self-registered; instead,
registration information is scanned from its type library and added to the
installation. Registering the file enables its advertising information to be drawn
into the installation—if the file is not registered, then this advertising information
might not be present on the current computer, which means it cannot be
automatically added. See How Self-Registration Information is Captured on
page 142.
• Rescan advertising information during compile
Mark this to gather advertising information from the registry for the file
referenced in the Key Path field each time you compile the installation. This
overrides the Default to rescan advertising for new components checkbox
in Wise Options for this component.
• Import REG File
Specify a .REG file that contains registry information about the key path file. This
information is read into the component each time you compile.
Example: If the programmer who creates the key file for this component is not
the author of the installation, the programmer can place all required information
into a .REG file and give this file to the installation author for inclusion into the
component. You can use WiseComCapture.exe to create this .REG file. See Using
WiseComCapture.exe on page 143.