This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Setup does not wait for PreRequisite to complete before checking the condition again
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 23, 2017
08:23 AM
Setup does not wait for PreRequisite to complete before checking the condition again
When running a setup that contains one ore more prerequisites that were built with InstallShield 2016, immediately when the first prerequisite starts installing, the 'Installation of xxx has failed. Continue with setup?' dialog is shown.
I've found that this is caused by the fact that the prerequisite setup now clones itself and launches that clone. While there may well be valid reasons for doing so, one would expect that the original behavior would be maintained and that the cloning setup would wait for the cloned setup to complete, before returning.
Although the /clone_wait command-line option can be added in each of my .prq file, there's no valid reason for introducing such a breaking change. It also requires to rebuild each setup that contains an updated prerequisite, where we used to be able to silently update them and just ship a new version along with an existing setup.
Also, when using /clone_wait, the dialog with the prerequisites that require installing, is closed when the /clone_wait-prerequisite completes.
Is there another way to make setups wait for the clone they (might) create?
I've found that this is caused by the fact that the prerequisite setup now clones itself and launches that clone. While there may well be valid reasons for doing so, one would expect that the original behavior would be maintained and that the cloning setup would wait for the cloned setup to complete, before returning.
Although the /clone_wait command-line option can be added in each of my .prq file, there's no valid reason for introducing such a breaking change. It also requires to rebuild each setup that contains an updated prerequisite, where we used to be able to silently update them and just ship a new version along with an existing setup.
Also, when using /clone_wait, the dialog with the prerequisites that require installing, is closed when the /clone_wait-prerequisite completes.
Is there another way to make setups wait for the clone they (might) create?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 16, 2018
09:20 AM
Just curious as to whether you ever got this resolved, and if so, what as the resolution?