Hey everyone!
Im having an issue currently that im trying to figure out. We have two chained MSI installers in our app, and they install the drivers for our products.
Running the installer normally works as intended.
However, the way our app is coded is for updates, it checks a manifest file, and if there is a driver update, our app will tell you to unplug your devices, and then it will proceed. it will close the app and proceed with install (this isn't super important but the process order is for understanding)
Our app for updates, just runs the installer in silent mode, so the user has no interaction, it just looks like the app updates without them seeing the installer windows at all. the problem I am encountering, is that for some reason, the app is being launched before the chained MSI packages have finished installing, which can be confusing to users, but if they are quick to plug back in their devices, the drivers wont update, causing more issues.
Hoping someone can point me in the right direction so that if its a silent install, it will complete the chained MSI packages, and THEN launch the app.
appreciate the help!
-Dricksus
Suggested Articles
Re: Launching App after chained msi installers complete
Hello! just bumping this in hopes of getting some feedback!
-Dricksus
-Dricksus
Re: Launching App after chained msi installers complete
Hi,
A workaround solution would be NOT to configure your prerequisites as chained packages. When using the chained packages feature the chained setup installation is fully handled by Windows Installer and this is done asynchronously of the main setup install. This is why your application is launched before the chained packages installations finishes.
So, you can proceed like this:
1. go to "Custom Actions" and add a "Launch file" custom action without sequence configured to launch your app
2. go to "Prerequisites" page and select your chained package item; go to "Installation" tab and uncheck the "Chained" flag
3. go to "Files" tab and in the "Action to be run after this package installation" combo box select the "Launch file" custom action
4. save and rebuild your setup project
Hope this helps.
All the best,
Daniel
A workaround solution would be NOT to configure your prerequisites as chained packages. When using the chained packages feature the chained setup installation is fully handled by Windows Installer and this is done asynchronously of the main setup install. This is why your application is launched before the chained packages installations finishes.
So, you can proceed like this:
1. go to "Custom Actions" and add a "Launch file" custom action without sequence configured to launch your app
- screen1.png (176.07 KiB) Viewed 8070 times
- screen2.png (211.47 KiB) Viewed 8070 times
- screen3.png (225.76 KiB) Viewed 8070 times
Hope this helps.
All the best,
Daniel