Build output files
Each package generates a number of files during the build in addition to the installer itself. Some of the files are only built if a certain option is set, others are always built but are automatically deleted at the end of the build process.
The files are placed in a special folder structure that keeps all distributable files of a configuration together and separate from other projects that you might have defined. In the following overview:
- Names in italics are placeholders for names that depend on the project or package.
- Intermediate files are temporary files that are generated during the build process, but cleaned up afterwards (unless you check the Keep intermediate files box in the Build - Advanced dialog box).
- Optional files are files that are only generated if you select a particular option.
Note: The following overview assumes default build output paths. You can override the build output paths through the Build folder option and others in the Build - Advanced dialog box. If you do, then the build output tree changes accordingly.
Project.im9 - Your InstallMate project file Project.log - The build log file is written in the same folder Project\ - A subfolder with the project's name is automatically created PackageName.SignCode.log - [Optional] the output from the most recent code signing PackageName(ProductVersion)-Manifest.xml - [Optional] the build manifest for the package PackageName(ProductVersion)-PackList.txt - [Optional] the packing list for the package PackageName\ or PackageName-xxxx\ - A subfolder with the package's name is automatically created (see note) Installer.exe - Your installer Installer.msi - [Optional] the installer wrapped in a Windows Installer package Installer.dat - [Intermediate] the installation database (do not distribute) Installer32.dll - [Intermediate] the 32-bit installer resources (do not distribute) InstallerX64.dll - [Intermediate] the x64 installer resources (do not distribute) Installer.txt - [Optional] the TWU update file for the installer Installer.zap - [Optional] the ZAP file for the installer Disk0001.tiz - [Optional] installation archive for the first disk Disk0002.tiz - [Optional] archive continuation for the second disk Disknnnn.tiz - [Optional] further archive continuations for disks 3..n Downloads\ - [Optional] subfolder that contains all download archives *.tiz - ...Compressed download files that must be placed on your server Target System\ - [Optional] subfolder that is the root of the uncompressed files and folders tree ... - ...Uncompressed files and folders are stored under Target System
Note: For multilingual installers, a single PackageName\ folder is created. For per-language installers, a separate PackageName-xxxx\ folder is created for each language, where xxxx is the 4-digit hexadecimal language code.
Any uncompressed files are stored in the same folder structure as that in which they appear on the Files and folders project page. The root of the uncompressed files tree is formed by a subfolder called Target System in the package's output folder; this corresponds to the Target System root node on the Files and folders project page. The other folders are created under the Target System subfolder. Only folders that contain uncompressed installation files will appear here.
The file and folder names used in the plain file tree are the same as their installation names. Because these installation names may be localized, the actual names in the plain file tree are also localized. This may cause problems if you are creating a multilingual installer as opposed to per-language installers:
- For multilingual installers, the default file and folder installation names are used (see the section Working with localizable attributes in the Attribute panes topic for an explanation of default and localized text strings);
- For per-language installers, the actual localized file and folder names are used (and are stored under per-language PackageName-xxxx build folders) .
In practice this is usually a non-issue, because most installation file names are not localized anyway. However, if your installer is distributed in several languages and you need to have the correct localized file and folder names in the plain file distribution, then we recommend that you select the Languages: Per language option in your package.
When you distribute your installer, you must include the following files and folders in the same relative locations as they were created during the build. Do not distribute any of the files that are marked "Intermediate" in the overview above; they will be present in the installation package anyway and their exposure might compromise the integrity of your installer.
Disk 1 (or other non-disk medium)
- The Installer.exe or Installer.msi installation file (choose only one);
- Optionally, the Installer.txt TWU update file (in the same folder as Installer.exe; not used for Installer.msi);
- Optionally, the Installer.zap ZAP file for the installer (in the same folder as Installer.exe; not used for Installer.msi);
- Optionally, the Disk0001.tiz file, if it exists (Disk0002.tiz and up must go onto additional disks);
- The entire Target System subtree, if it exists (must start in the same folder as Installer.exe/Installer.msi).
Disks 2..n (only present if disk spanning is in effect)
- The applicable DiskXXXX.tiz files; Disk0002.tiz on the second disk, Disk0003.tiz on the third, and so on. If there is a Disk0001.tiz file, it should be placed on the first disk, alongside the main installer.
Tip: If for some reason the span size that you specified is less than the actual disk size that you use, then you can place multiple DiskXXXX.tiz files on a disk, including the first one. However, you should assign the files to disks in ascending order to minimize the number of disk prompts for the customer.
Your Internet server (if any components are marked for downloading)
- All files from the Downloads folder, in the location that you specified in the Download URL field.