|
|
||
MSI Factory
Tip: For information on the possible return codes from the automatically generated script for the bootstrapper, see the topic Bootstrapper Script Return Codes.
Tip: In the standard bootstrapper script, you can enable logging in the MSI file by passing the command line option: /LOGMSI:<full path and filename of log file>
Embed the setup MSI file inside of the bootstrapper. In this case you will not have to distribute the setup MSI file separately. This option should only be used if you generated a single MSI file that contained its cab files internally. You can configure how cab files are included in your setup from the Media dialog.
If checked, your setup file will be able to be extracted by running the bootstrap executable and passing "/EXTRACTMSI:<full path and filename>" on the command line. This can be useful when a system administrator wants to deploy your MSI file outside of the executable. In most cases, you should keep this option checked.
Run the MSI file from the same folder that the bootstrap executable is located in. This option is good if you are doing a multi-disk installer or if your files or cab files are external to the MSI file.
Download the MSI file from your Web site. In this case the MSI file should be self-contained (all cab files should be embedded within the MSI file). The file will be downloaded to the local system if necessary and run. The connection will be made on port 80. Proxy settings will be automatically detected at runtime.
The full URL to the file to download.
The requested execution level that should be written into the bootstrap executable's internal manifest. In general, you should select "requireAdministrator" as this will offer you the advantage of having your MSI file run elevated immediately. This setting will have no effect on pre-Vista versions of Windows.
Learn More: Indigo Rose Software - MSI Factory - Buy Now - Contact Us