Hi Swati,
Let me explain you how we support the “Feature based” prerequisite:
Full UI installation package:
- -We have a synchronous custom action in the “Install UI sequence” . This is required because you cannot have two .msi packages running in install UI sequence.
Silent installation package:
- -We have an .EXE custom action, asynchronous execution which is launched after the install execute state from the main package ends. We do this because for silent installation there is no UI sequence, so we cannot schedule a custom action to be executed before install execute sequence starts.
Since you need to install the prerequisite before the main installation package then you can added them as
“Pre-Install”. The
Pre-Install prerequisite are handled by bootstrapper in separate process. After the prerequisite finish installation then the .msi package is launched by the bootstrapper.
You can try to remove the
Pre-Install prerequisites through a custom action from the main installation package when the main installation package is uninstalled. You need to set this custom action after the
Finish Execution stage and disable the
Wait for custom action to finish before proceeding and
Wait for return code at the end of the sequence options from the
custom actions properties. The custom action that will trigger the prerequisite uninstall will only run on
Uninstall.
If you have other questions, please let us know.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging