Comments on: Feature states in component conditions

By: Bob Arnson

Bob Arnson — Fri, 26 Sep 2008 14:37:26 +0000

Schedule the custom action before CostFinalize.

By: Sergey S

Sergey S — Thu, 25 Sep 2008 10:16:57 +0000

Sorry, forgot to escape the code:


	&Feature2=3
...

By: Sergey S

Sergey S — Thu, 25 Sep 2008 10:11:27 +0000

Thanks, Bob!

Yes, components can be assigned to multiple features but this works as logical-OR (if at least one feature is selected the component will be installed). My scenario is a little bit different. The component (say ComponentA) is linked to feature Feature1. But i need to install it only if users select both Feature1 AND Feature2 so i add the following condition:

&Feature2=3 ...

This doesn’t work (however Feature2 state is 3 for sure). Then i scheduled the following CA to run:

NOT Installed AND

which sets InstallFlag property (realy sets according to the log) so i can check it in the component’s condition like

InstallFlag

And this also doesn’t work It only works if the property is predefined but i do need dynamic condition. What whould you suggest?

By: Bob Arnson

Bob Arnson — Thu, 25 Sep 2008 02:20:59 +0000

Sergey,

It’s possible — just add the component to the feature. Components can be assigned to multiple features. The problem is in trying to use feature conditions for mutually-exclusive components. That doesn’t work.

By: Sergey S

Sergey S — Wed, 24 Sep 2008 20:04:54 +0000

Looks like it’s not possible to install a component only if a specific feature has been selected to install (using feature state in component condition)? How in this case people solve the problem?

By: Bob Arnson

Bob Arnson — Thu, 18 Sep 2008 06:04:53 +0000

This entry was about trying to mix feature states in component conditions. Using feature states elsewhere works, within the limits described in the doc. See http://msdn.microsoft.com/en-us/library/aa368561(VS.85).aspx for examples.

By: Chris B

Chris B — Wed, 17 Sep 2008 16:25:41 +0000

Great article – but this article only covers the doumentation, have you been able to find a single example of how to do this at all? I not only have a component I’d like to be able to install based on another Feature’s state, but I also have a dialogbox I’d like the user to see ONLY if they install a Feature. I’m using InstallShield 2008, but I can do a direct-edit if I have to.

Why isn’t this easier? I mean seriously, there have to be countless people like me who have a simple feature-based installer where, say, they have to install a SQL script, but if the user chooses not to install SQL script at that time, we *don’t need* a SQL script login dialog box.

Please, leave a comment or drop me a line if you’ve seen examples of how precisely to do custom actions based on Feature states…