How to Package an Application which contains Multiple installers inside and each installer requires a reboot then triggers next installer ??
I have come across this question during one of the discussion on application packaging.
My approach was as below to answer this scenario:
1. If Application contains the installers in MSI format use the MSI silent commands and suppress the reboot.
2. If it is an legacy setup then use the RunOnce key.
I am not sure if I understood the scenario completely as I am still a kid in Application Packaging. Any further explanation and answers will be very much appreciable.
Answers (1)
If it's a legacy installer, re-package it. I'd want to know what the vendor is going to do with my patiently-crafted build, thank you very much!! Ha, ha, ha!
For any package, find out why the reboot is being requested, remembering that most vendors are extremely dumb and think a reboot is their only option when, more often than not, it's not necessary at all.
Comments:
-
Thanks for your reply.
Just want to know, whether Admin Studio or Wise Package Studio are able to handle reboot in this senario ? - The_D 10 years ago-
Which tool you use is irrelevant. Besides, you can discount Wise as it's a dead product. - anonymous_9363 10 years ago
