Summary
Working with Legacy Installer Packages in the Application Catalog and Compatibility Testing
Synopsis
This is information about working with Legacy Installer Packages in the Application Catalog and Compatibility Testing.
Discussion
Application Manager supports the import of non-MSI legacy setup types (such as InstallShield Professional or ISMP installations) into the Application Catalog. By importing these legacy setup formats, you allow AdminStudio to manage these setups in a manner consistent with other MSI based packages.
Groups of tests can be executed against the Windows Installer, App-V, Apple iOS, or Google Android package types in AdminStudio 2015 and later.
Using AdminStudio 2016 and later the setup.exe must be a bundled MSI install. This implies AdminStudio technology can extract the various MSI file(s) out of the setup.exe to run tests using the Test Center. The expected way the legacy exe can be tested is when the MSI can be extracted. This is considered a bundled installer.
Workaround
To work around using legacy setup.exe files here are some options:
- Repackage the legacy setup.exe and import and run tests against the repackaged installer.
- Obtain the MSI from Vendor. Some vendors have installers for you in MSI format.
- Extract the MSI from the compressed setup.exe and import.
Furthermore, AdminStudio 2016 and later offers some support for legacy exe files with a number of considerations.
- The setup.exe must be a bundled MSI install. This implies AdminStudio technology can extract the various MSI file(s) out of the setup.exe to run tests using the Test Center. Again, the only way the native exe can be tested is if we can extract the MSI and we consider this a bundled installer.
- Same work around above - take your legacy exe and repackage it.
Additional Information
Please review these references: