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
- :
- How to define condition not to run an installshield prerequisite
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
Nov 29, 2011
03:53 AM
How to define condition not to run an installshield prerequisite
We were using Visual Studio bootstraps (VS2010 deployment project) for all our prerequisites.
I try to convert a bootstrap's product.xml (coming from 3rd-party maker) to InstallShield Prerequisite using Prerequisite editor which allows the defintion of conditions.
The condition checks an entry in the registry for a version v. If the version = v it skips the install, if the version is < or > to v it fails and it installs otherwise.
The editor only allows run condition. How can I state failure condition (i.e. older or newer version exists)?
I try to convert a bootstrap's product.xml (coming from 3rd-party maker) to InstallShield Prerequisite using Prerequisite editor which allows the defintion of conditions.
The condition checks an entry in the registry for a version v. If the version = v it skips the install, if the version is < or > to v it fails and it installs otherwise.
The editor only allows run condition. How can I state failure condition (i.e. older or newer version exists)?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 29, 2011
01:39 PM
InstallShield prerequisites are not quite that flexible. You can specify a condition that indicates you need to install the prerequisites, and if the evaluation of that condition changes after installation, the prerequisite succeeds. You can couple this with a System Search and LaunchCondition or similar check to verify in the main install whether this package is properly present.
If you can use the new Suite projects, you can more completely model this scenario. I would use an eligibility condition of Any(no-version, matching-version), a detection condition of matching-version, and an Exit Condition on the package if you want to abort when the package is not eligible.
If you can use the new Suite projects, you can more completely model this scenario. I would use an eligibility condition of Any(no-version, matching-version), a detection condition of matching-version, and an Exit Condition on the package if you want to abort when the package is not eligible.