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
- :
- Create a custom software condition in installshield
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
‎Apr 12, 2012
12:30 AM
Create a custom software condition in installshield
Hi,
i need to check registry settings before installing a setup, for qwhich i need to add a custom software condition.Can any one plese guide me how to do it???
i need to check registry settings before installing a setup, for qwhich i need to add a custom software condition.Can any one plese guide me how to do it???
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 12, 2012
02:16 AM
In premier/pro edition you can use System search to check for the existence of the registry key and store that value in a public property.
Use this property in the Install Condition section under General Information.
That's it!!
Use this property in the Install Condition section under General Information.
That's it!!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 04, 2012
11:02 AM
I'm trying to do this same thing and the condition always fails when it should pass. I'm not sure if the registry search is bad or if the condition logic is bad.
I have a property called VISIONPATH that has a default value of "asdf". So first AppSearch runs to set my registry data to VISIONPATH. The log shows this result...
Does that mean it found the registry value or not?
Then my install condition, which uses
Any ideas?
I have a property called VISIONPATH that has a default value of "asdf". So first AppSearch runs to set my registry data to VISIONPATH. The log shows this result...
AppSearch: Property: VISIONPATH, Signature: NewSignature1
Action ended 8:35:54: AppSearch. Return value 1.
Does that mean it found the registry value or not?
Then my install condition, which uses
VISIONPATH <> "asdf", says that the value is still "asdf". So the installer quits.
Any ideas?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2012
11:10 AM
Turns out I found a solution for me at least. I went into Direct Editor and in the RegLocator table set the "Type" for my registry search to 2.
After that the AppSearch was able to find and set my property to the registry data.
After that the AppSearch was able to find and set my property to the registry data.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)