Hi,
I'd like to know the difference of Repacker feature under Architect license and "Convert exe installers to MSIs" feature under Enterprise license. Currently what we want to achieve is to create an MSI installer for the existing installation package that we have. Basically this installation package is not an MSI installer and we want to use AI to convert it. Please shed some light on how to do it via AI and what license to use to achieved it.
Thanks in advance
Suggested Articles
Re: Repacker vs convert to MSI
Hello,
Indeed, Advanced Installer can convert an EXE installation package to a MSI installation package.
In order to achieve that you can use :
The import operations allow you to create standard Windows Installer-based MSI packages by capturing and reproducing the behaviour of the original installers or installer projects.
If you want to convert an existing .EXE to a .MSI, you can follow the steps which are described in our Convert EXE(s) to MSI article which will guide you in creating a .MSI installation package which installs existing .EXE packages.
You can download Advanced Installer and test the trial. During the trial you have access to all the features, without any limits. The setup packages will just include message boxes during the installation, saying they were built with a trial version of Advanced Installer. Other then that, you can change dialog backgrounds, branding, anything you want.
Just make sure you create the project type you need, as the features are limited based on the project type.
Should there be any difficulty you encounter implementing something, please do not hesitate to contact me and I will gladly assist.
Best regards,
Dan
Indeed, Advanced Installer can convert an EXE installation package to a MSI installation package.
In order to achieve that you can use :
- 1) Convert EXE(s) to MSI support which will create a .MSI installation package which installs existing .EXE packages.
2) Repackage Installation support which will create a project based on capturing an existing installation.
3) Repackage Installation in a virtual machine support which will create a project based on capturing an existing installation in a virtual machine.
The import operations allow you to create standard Windows Installer-based MSI packages by capturing and reproducing the behaviour of the original installers or installer projects.
If you want to convert an existing .EXE to a .MSI, you can follow the steps which are described in our Convert EXE(s) to MSI article which will guide you in creating a .MSI installation package which installs existing .EXE packages.
You can download Advanced Installer and test the trial. During the trial you have access to all the features, without any limits. The setup packages will just include message boxes during the installation, saying they were built with a trial version of Advanced Installer. Other then that, you can change dialog backgrounds, branding, anything you want.
Just make sure you create the project type you need, as the features are limited based on the project type.
Should there be any difficulty you encounter implementing something, please do not hesitate to contact me and I will gladly assist.
Best regards,
Dan