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
- :
- Automation Interface and Merge Modules
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 20, 2009
03:21 PM
Automation Interface and Merge Modules
Is there a way to configure a merge module after adding it to a feature using the automation interface?
It doesn't seem like there are any types available to describe a merge module and the add/remove members only take strings as an argument along with no collections being exposed to indicate which modules belong to a feature.
Am I missing something or is this part of the API just really not there?
It doesn't seem like there are any types available to describe a merge module and the add/remove members only take strings as an argument along with no collections being exposed to indicate which modules belong to a feature.
Am I missing something or is this part of the API just really not there?
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 21, 2009
11:27 AM
Unless they're part of ISWiFeature.ISWiObjects (which I would not expect), this API is probably just missing. This feature request is being tracked under IOC-000072904.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 26, 2009
12:59 PM
Michael-
Do you know how to add a condition to a feature? I'm looking at the ISWiFeature and ISWiCondition objects and I'm not getting it. The Conditions collection doesn't seem to implement add and remove members and the Add/Delete condition members of the Feature class take a string key which I have no idea how to construct.
It seems like something is missing to me.
BTW, am I correct in assuming that the IS IDE doesn't actually use it's own automation interface? It seems like every single time I try to use this part of InstallShield functionality is either missing or broken.
Do you know how to add a condition to a feature? I'm looking at the ISWiFeature and ISWiCondition objects and I'm not getting it. The Conditions collection doesn't seem to implement add and remove members and the Add/Delete condition members of the Feature class take a string key which I have no idea how to construct.
It seems like something is missing to me.
BTW, am I correct in assuming that the IS IDE doesn't actually use it's own automation interface? It seems like every single time I try to use this part of InstallShield functionality is either missing or broken.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 26, 2009
01:07 PM
OK, I figured it out but jeesh. How am I supposed to know the "sConditionKey" is the conditional expression? In fact, if the AddCondition member is a wrapper for functionally constructing the condition, why not have an InstallLevel argument also?
Oh this API kills me.... 😞
Oh this API kills me.... 😞
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 27, 2009
01:53 PM
I'm glad you found what you needed. Our automation layer design predates me, so I can't comment too usefully on that. But I hear you. It's a layer which wraps our internal automation, I believe with the intent to protect people from some of the worst authoring mistakes our internal automation allows. As you've noticed, this means it can be out of sync with our IDE's capabilities.