Using custom actions can I install the vendor supplied MSI before the main package?Bogdan wrote: 1) you can use a custom action under the InstallFinalize phase in the second MSI to install the vendor supplied MSI. In the Execute Properties group you should select the "Asynchronous execution, do not wait for return code" radio button.
I've tried importing the vendor-supplied MSI, but the build is corrupt right after a default import.Bogdan wrote: 2) you can import the MSI file using the File -> Import -> Import MSI/MSM option.
I tried this and it didn't install the prerequisite. After I added the prerequisite, Adv Installer ticked create .exe, which I deselected because I want an MSI, an EXE is not required.Bogdan wrote: 3) you can try using the Prerequisites page. You can add the first MSI file to the Software Prerequistes tab and set the appropriate Install Conditions. This will make the package to install if it doesn't already exist on the target machine.
Yes, but only if you schedule the custom action under the InstallUISequence and not under the InstallExecute Sequence. Also in the Execute Properties group you should select the "Asynchronous execution, wait for return code at the end of the sequence" radio button.Using custom actions can I install the vendor supplied MSI before the main package?
Please note that the import features in Advanced Installer (the Repackager, the Import MSI feature etc.) are intended to be used to get a starting point for your installation package, not to completely reproduce other installation packages.ve tried importing the vendor-supplied MSI, but the build is corrupt right after a default import.
Please note that to install the prerequisites it is required that you create an .exe package. This will first install the prerequisite(your vendor supplied msi) and after that extract and install the main package.I tried this and it didn't install the prerequisite. After I added the prerequisite, Adv Installer ticked create .exe, which I deselected because I want an MSI, an EXE is not required.
msi_user wrote:Using custom actions can I install the vendor supplied MSI before the main package?
When I attempt to add a custom action to the InstallUISeqence section the options are greyed out (unavailable). Any idea why?Bogdan wrote: Yes, but only if you schedule the custom action under the InstallUISequence and not under the InstallExecute Sequence. Also in the Execute Properties group you should select the "Asynchronous execution, wait for return code at the end of the sequence" radio button.
When I do that the MSI options are unavailable. Only ".exe", ".vbs", etc are available.Bogdan wrote: To be able to add a custom action under InstallUISequence you need to display at least one standard action from that tree. For example you can display Begin standard action like this:
-- right click InstallUISequence
-- Show Standard Action -> Begin
Now you can right click on Begin phase and add the custom actions you desire.
You do not need to use the MSI options. Please follow these steps:When I do that the MSI options are unavailable. Only ".exe", ".vbs", etc are available
Code: Select all
"[&Vendor_Package.msi]"
FOLLOW US
Get the latest news in Application Packaging