Install Files

This command is used to install files on the target system.

Source Files

Provide the full or relative path to the files to install. Relative paths will be resolved relative to the project folder. These files must exist on your development system and therefore no runtime script variables are allowed in this field. Only a string literal may be used here, but wildcards, compiler variables, and environment variables are supported as part of the string literal. This field will be resolved at compile time to the actual files found on your system by the compiler. Check the Include subfolders if wildcards used checkbox to perform a recursive operation.

Exclude Wildcards

If you would like to exclude some of the files matching your source file pattern above, you may do so by specifying exclude wildcards. Exclude wildcards allow you to filter out some files at build time from inclusion in your setup. Leave this field empty if you do not wish to exclude any files. If you wish to exclude a particular file, folder, or a collection of files and/or folders, enter the name(s) of the items to exclude here. You may use wildcards. Seperate multiple items using semi-colons. Remember to enclose items that contain spaces in their names inside double quotes.

Target Folder

Provide the full path to install the files on the target system. This field should not be left empty.

Set Attributes

Check each of the file attributes you wish to set on the files after they have been installed on the target system.

File Properties

Check the relevant file properties for the files you are installing. The checksum property is ignored by the Native Engine.

Copy Options

Check all the desired file copying and removal safeguides.

 Notes

• For accurate disk space requirements, please see the comments following the Get Component State command.
• The Windows Installer engine behavior is to overwrite files on the target system only if the ones you are copying are newer. This behavior cannot be changed with the Windows Installer engine.
• Similarly, the Native Engine by default will not overwrite files on the target system if the ones you are copying are not newer, however overwrites may be forced by setting the pre-defined variable NATIVE_OVERWRITE_OLDER to TRUE. However, this is not recommended as it may compromise target system integrity and may break other applications.
• If you checked File is Self Registering DLL, remember that all files that the Install Files command pertains to must be self registering. If a self registration error occurs, the Windows Installer engine will roll back the entire installation as part of its resiliency mechanism. The Native Engine will not roll back unless the end-user cancels the installation when the self registration error is reported.
• The Windows Installer engine does not perform self registration for executable files, or across reboots. The Native Engine handles both cases successfully.
• With the Windows Installer engine, if files you are installing require to be self registered in a particular order, do not check the File is Self Registering DLL option. The Windows Installer engine does not allow the self registration order of files to be specified. Instead, use the Register Library command to manually self register those files.
• The above limitation does not apply to the Native Engine. Self registering files will be self registered in the exact order of execution as found in your MSIcode script.
• If you checked File is Vital for Installation, setup will not succeed unless the files in question are selected for installation and successfully installed.