Primer files are just regular files that get extracted from the setup executable before the installation process begins. This means you can use primer files at the very start of the installation process, right after the user runs the setup executable.
You can make any file a primer file simply by adding it to the Primer Files tab of the General Design dialog. The files on this tab will be included in the setup executable when you build the installer.
Primer files are automatically extracted to a temporary folder at run time. The path to this folder is stored in a built-in variable named %TempLaunchDir%. You should use this variable in actions that need to access your primer files.
Primer files make it easy to run a program on the user's system before the rest of your files are installed. Just add the program to the list of primer files, and execute it with an Execute File action early in the installation process.
For example, you might need to execute a custom program or DLL function before your software is installed-perhaps to perform some product-specific, low-level pre-installation tests on the user's hardware, and write the results to the Registry. By adding your custom program or .dll to the list of primer files, you could distribute it "inside" your setup executable and still be able to run it before any of the "normal" files in your project are installed.
TIP |
|
|
|
|
Another way to access files at the start of the installation process
is to distribute them "alongside" your installer. For
instance, you could store the files "externally" on the
same CD-ROM, and access them directly; or, you could download the
files from your web site using a Download
File HTTP action on the Startup
action tab. Primer files are only required when you need early access, and you want the files to be included in your setup executable. |
NOTE |
|
|
|
|
Primer files must be deleted manually using actions - they are not removed automatically at the end of an installation. |
See Also: Primer Files tab