Build Tab (Project Properties Dialog Box)

Options

Output file name

Accept the default package file name, or change it by typing a different name.

Output folder

Specify the source machine folder where your installer project outputs are placed when you build the installer project. You can accept the default folder shown (named Output in your installer project directory), or click Browse to change it. Browse leads you to the Browse for Folder dialog box, where you can navigate to and select a different project folder.

When you create an .msi file, Microsoft^® Visual Studio^® Installer creates an image of each disk in the project's output directory, and sequentially labels these images as subfolders Disk_1, Disk_2, Disk_3, and so on. You must label the corresponding installation floppy disks according to this sequence and format.

Build type

Select which type of package file to build from the drop-down list:

Installer. This is a self-installing Microsoft^® Windows^® installer package file containing all information necessary for the installation of your application.
Installer with Windows Installer Loader. This creates an installer package file with a Windows installer bootstrap loader (setup.exe file). The bootstrap loader checks to see if the Windows installer is already on the target machine. If not, the bootstrap loader installs the correct installer for the target machine's operating system. For example, the bootstrap loader would install the Microsoft^® Windows NT^® installer on Windows NT machines.
The bootstrap loader runs the installer package file after checking for (and, if necessary, installing) the Windows installer.
Building an installer with the Windows installer bootstrap loader creates these distinct files as part of your installer package:
- Your .msi file.
- Setup.exe, the file that determines whether or not the Windows installer resides on the target machine and installs the Windows installer if necessary.
- Setup.ini, the file that tells setup.exe the name of your .msi file to install.
- Instmsiw.exe, the Windows installer for Windows NT machines.
- Instmsia.exe, the Windows installer for Windows 95/98 machines.
Merge Module. This is a Windows installer Merge Module (.msm File), the recommended method for sharing code among Installer Package (.msi) File.

For more information about installer package files and merge modules, see Installer Package Files and Merge Modules.

Package files as

Select the appropriate installer package file type from the drop-down list available here. This field is not available if you are creating a merge module.

Available package file types include:

Compressed in setup file. Creates a single installer package file that includes all necessary compressed cabinet (.cab) files.
Compressed in cabinet file(s). Creates an installer package file and, separately, any necessary compressed .cab files.
Uncompressed. Creates a single installer package file and, separately, all uncompressed individual files required for the application installation.

Compression

Accept the default compression type or select another from the drop-down list available here.

Optimized for speed. This is the default option. This selection decreases the time required to build your compressed .msi file but increases its size.
Optimized for size. This selection decreases the size of your compressed .msi file but increases the time it takes to build it.
None. Your .msi file is not compressed.

Media

Select the appropriate media type and size for your package file from the drop-down list available here. Media options are only available for installer package (.msi) files with the Package files as option set as Compressed in cabinet file(s) or Uncompressed.

Available options include:

Unlimited. Specifies distribution over a network, where there is no physical distribution media. No media size is specified, so your package file will be bundled as a single packet.
CD (640M). Specifies distribution on a CD-ROM with the default media size of 640 megabytes (MB). If your package file is larger than 640 MB, it will be bundled in packets of up to 640 MB each. Output folders are created for each disk.
Floppy (1.44M). Specifies distribution on floppy disks with the default media size of 1.44 MB. If your package file is larger than 1.44 MB, it will be bundled in packets of up to 1.44 MB each. Output folders are created for each disk.
Important The Windows installer requires that installation floppy disks are labeled sequentially, in a specific labeling format. If you package your installer on floppy disks, you must label the first floppy (the one maintaining the .msi file) Disk_1. You must also label any remaining installation floppy disks in the sequence users will be prompted for them — for example, Disk_2, Disk_3, and so on.
Custom (single disk). Specifies distribution of installation files (typically, .msi and .cab files) on a single disk of some type of media other than CDs or floppy disks, such as an Iomega Zip disk or the Web.
If you select Custom (single disk), you must specify this information in this field:
- Media size, the maximum size (in kilobytes) of packets to bundle your installation files in.
  Important With Custom (single disk) packaging, successful installation requires that all .cab files to be installed reside in the same directory as your .msi file.
Custom (multiple disks). Specifies distribution on multiple disks of some type of media other than CDs or floppy disks, such as Zip or Iomega Jaz disks. Folders are created for each disk, and each folder typically contains complete .cab files or the .msi file. As with floppy disks, you must label installation disks to exactly match the names of the output folders Visual Studio Installer creates — for example, Disk_1, Disk_2, Disk_3, and so on.
If you select Custom (multiple disks), you must specify this information in these fields:
- Media size, the maximum size (in kilobytes) of packets to bundle your installation files in.
- Cluster size, in bytes.

Apply

Accept the build properties shown, and do not close the Project Properties dialog box.