Creating Multiple, Platform-Specific Installations From One Project File - Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Creating Multiple, Platform-Specific Installations from One Project
File
Windows Installer Editor Reference
64-bit Installations That Contain Some 32-bit Components
Select the appropriate target platform for each feature, and add the correct type of
component to each one. Do not add a 64-bit component to a 32-bit feature, and
vice versa, because it will never be installed.
When you add 64-bit .EXE and .DLL files or 64-bit registry keys, they are designated
as 64-bit components. (The 64-bit component check box is marked on the
Component Details dialog box.) When you add 32-bit files or registry keys, the 64-
bit component check box is not marked.
Select the appropriate target platform for each release.
AMD 64-bit computers require Windows Installer version 3.0 or later. If your
installation targets AMD 64-bit computers, include a system requirement to check
the destination computer's Windows Installer version.
You can create a single installation project (.WSI) that can produce 32-bit and 64-bit
installation files.
See

Creating Multiple, Platform-Specific Installations from One Project File

Platform-Specific Merge Modules
A 32-bit merge module can be merged into a 32-bit or 64-bit installation.
A 64-bit merge module can be merged into a 64-bit installation. The processor type
(x64 or Intel64) of the merge module must match that of the installation.
See also:
How to Specify the Target Platform
Using 64-bit Merge Modules in the Windows Installer SDK Help
You can create a single installation project (.WSI) that can produce 32-bit and 64-bit
installation files, or x64 and Itanium installation files.
Example:
You develop a graphics suite that consists of features for drawing, graphing, and page
layout. The application was originally developed as a 32-bit application, and you will
continue to support a 32-bit version, but you also will release a version that contains
some 64-bit components. To save development time, you want to maintain a single
installation project (.WSI) that can produce installation files for both platforms.
Your options are:
Organize the project by feature. Do this to let the end user choose from different
platform-specific features during installation. In a large installation, this method will
work better than organizing the project by component.
Note
If you add a 64-bit component to a 32-bit feature, it will never be installed. A 64-bit
component will be ignored during installation on a 32-bit computer, and a 32-bit
feature will not be installed on a 64-bit computer.
Working With Wise Installation Files
on page 71
on page 75.
75