Configuring Advanced Conversion Options
AdminStudio 2021 R2 | 22.0 | Repackager
Edition:This feature is available in AdminStudio Professional and Enterprise Editions.
To set package conversion and component settings in your Repackager project, perform the following steps.
To configure advanced conversion options:
| 1. | Select Advanced Settings from the Repackager View List. The Advanced Package Settings view opens. |
| 2. | Under Package Conversion, select the package conversion options you want to use during conversion: |
|
Option |
Description |
|
Use Editor path variables instead of physical source paths |
When storing files in the InstallShield Editor project (.ism), the Wizard uses path variable locations whenever possible. |
|
Display only the Welcome dialog box during installation |
Only the Welcome dialog box is displayed when the Windows Installer package is run on a target machine. If this option is unchecked, the default UI sequence is displayed when the setup is installed. |
|
Replace files with merge modules wherever possible |
Following best practice rules, Repackager replaces components with comparable merge modules whenever possible. |
|
Use the language captured by the Repackager as the language of the setup |
When selected, the target package's language will be the language detected by Repackager (as displayed in the Captured Installation view). |
|
Include files from Setup Intent scan |
Any files identified when running the Setup Intent Wizard will be included in the package (unless you have manually excluded them from the project). |
| 3. | Under Component Settings, select the component settings options you want to use during conversion: |
|
Option |
Description |
|
Mark components destined for the System folder as permanent |
Executable files installed to the system folder (System32Folder) are marked as Permanent files and will not be uninstalled when the package is uninstalled. This eliminates ICE09 validation errors. |
|
Mark components destined for the CommonFiles folder as shared |
Executable files installed to the CommonFilesFolder (or a subfolder of CommonFilesFolder) are marked as shared files. This ensures that these components can coexist with DLLs installed by previous setups. |
|
Map registry data to the appropriate COM tables |
Setting this option reduces the number of ICE33 warnings that can occur during package validation, resulting from data not being mapped to the appropriate MSI tables. |
|
Map registry data to the appropriate ODBC tables |
If selected, ODBC-related registry data is mapped to ODBC tables instead of the Registry table. This data will only function correctly if Windows Installer supports the ODBC resource being mapped; it is recommended that you do not enable this option if you are unsure whether the ODBC resources are supported correctly by Windows Installer. |
|
Map NT Service events to the ServiceControl table |
If selected, NT Service–related registry data is mapped to ServiceControl table instead of the Registry table. |
See Also