General |
|
|
|
General |
|
|
General |
|
|
|
General |
|
|
|
|
||
MSI Factory
The unique ID of the component for use as the primary key in the MSI database's component table. This is a short, descriptive name such as "file1.exe" or "docs."
A GUID that uniquely identifies this component's contents, language, platform, and version. You can use the Generate button to create a new GUID. Note that you should not change the GUID of a component once it has been deployed in an installer unless something has happened to its contents to force it to be a new unique component (a file has been added or removed form the component, for example).
The condition that must be met in order for the component to be installed. If you are using operating system conditions on components you should check the "Transitive" checkbox below so that the condition is re-evaluated if the user updates their operating system.
If checked, the installer does not install or reinstall the component if a key path file or a key path registry entry for the component already exists. The application does register itself as a client of the component. Do not use this setting for components that contain files that have advertised AppIDs, TypeLibs, Classes, File Associations or ProgIDs.
If checked, the installer increments the reference count in the shared DLL registry of the component's key file. If this bit is not set, the installer increments the reference count only if the reference count already exists.
If checked, the installer does not remove the component during an uninstall. The installer registers an extra system client for the component in the Windows Installer registry settings.
If checked, the installer reevaluates the value of the statement in the condition field upon a reinstall. If the value was previously False and has changed to True, the installer installs the component. If the value was previously True and has changed to False, the installer removes the component even if the component has other products as clients.
Choose where the component should be run from:
Component cannot be run from source. Select this option for all components belonging to a feature to prevent the feature from being run-from-network or run-from-source. Note that if a feature has no components, the feature always shows run-from-source and run-from-my-computer as valid options.
Component can only be run from source. Select this option for all components belonging to a feature to prevent the feature from being run-from-my-computer. Note that if a feature has no components, the feature always shows run-from-source and run-from-my-computer as valid options.
Component can run locally or from source.
If checked, registry reflection will be disabled on all existing and new registry keys affected by this component. In this case the Windows Installer calls the RegDisableReflectionKey on each key being accessed by the component. This bit is available with Windows Installer version 4.0 and is ignored on 32-bit systems.
Note: 32-bit Windows applications running on the 64-bit Windows emulator (WOW64) refer to a different view of the registry than 64-bit applications. Registry reflection copies some registry values between these two registry views.
If checked, the component will be marked as a 64-bit component. This attribute facilitates the installation of packages that include both 32-bit and 64-bit components. If not checked, the component is registered as a 32-bit component. If this is a 64-bit component replacing a 32-bit component, check this option and assign a new GUID.
MSDN Online: Conditional Statement Syntax
MSDN Online: Defining Installer Components
MSDN Online: Organizing Applications into Components
MSDN Online: Registry Reflection
MSDN Online: Using Transitive Components
MSDN Online: What happens if the component rules are broken?
MSDN Online: Windows Installer Components
BLOG: Windows Installer Components Introduction
WiX Help File: Component Element
Learn More: Indigo Rose Software - MSI Factory - Buy Now - Contact Us