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
- :
- Re: Suite - feature condition
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
‎Oct 11, 2012
10:24 AM
Suite - feature condition
Hello,
I can't see the posibility to set the condition of a feature to a simple property compare.
Like: MyProperty=="0"
Can someone give me a hint?
Regards
Johannes
I can't see the posibility to set the condition of a feature to a simple property compare.
Like: MyProperty=="0"
Can someone give me a hint?
Regards
Johannes
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 12, 2012
09:14 AM
You'd need to set up an extension condition in order to do that. For more information, see the following help topics:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 12, 2012
11:02 AM
Hello Debbie,
thanks for your reply!
The Extension Condition DLL is very good idea for the rest of all conditions.
And it's workaround.
But I think, that the simple condition ( a property ) should be solved by a standard condition.
Regards
Johannes
thanks for your reply!
The Extension Condition DLL is very good idea for the rest of all conditions.
And it's workaround.
But I think, that the simple condition ( a property ) should be solved by a standard condition.
Regards
Johannes
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 12, 2012
11:15 AM
I logged this request as IOA-000074628 in our tracking system.
How would you use this type of condition; what sort of property do you envision checking in a condition?
Thanks!
How would you use this type of condition; what sort of property do you envision checking in a condition?
Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 15, 2012
05:53 AM
Hello Debbie,
the simplest posibility is a command line parameter.
And as long as I can set or change properties, e.g. in a dialog, it would be helpful, if these properties can have an influence on the package conditions and other conditions.
Regards
Johannes
the simplest posibility is a command line parameter.
And as long as I can set or change properties, e.g. in a dialog, it would be helpful, if these properties can have an influence on the package conditions and other conditions.
Regards
Johannes
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 21, 2012
04:17 AM
Hi guys,
Does anybody know how a feature action state (FEATURE[feature-name].actionState) could be accessed from and external extension (C++)?
I've tried the following but always getting an empty string back:
FEATURE[feature-name].actionState
FEATURE.feature-name.actionState
Also tried to store the action state in a variable ({SetProperty WebCompInit=FEATURE[feature-name].actionState}) before calling my custom code, but in that case I'm getting this from C++:
FEATURE.actionState
Any thoughts on this? :confused:
Thanks,
Attila
Does anybody know how a feature action state (FEATURE[feature-name].actionState) could be accessed from and external extension (C++)?
I've tried the following but always getting an empty string back:
FEATURE[feature-name].actionState
FEATURE.feature-name.actionState
Also tried to store the action state in a variable ({SetProperty WebCompInit=FEATURE[feature-name].actionState}) before calling my custom code, but in that case I'm getting this from C++:
FEATURE.actionState
Any thoughts on this? :confused:
Thanks,
Attila
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2012
09:22 AM
spUIExtension->get_Property / spUIExtension->put_Property using the first name that you mention (FEATURE[name].actionState) should work fine, unless there’s a typo.