Component condition evaluation - Please help!!
Posted 28 July 2005 - 00:05
I posted this in microsoft.public.windows.msi but thought i'd post here too.
I read in MSI documentation for Component Table that we can use feature
states in the expression used for component condition. So in my install
project, i'm trying to do the following:
comp1 &Feature2 <> 3
where comp1 is in Feature1. I was expecting that using this condition, comp1
will get installed only when Feature2 is NOT installed. But comp1 always
gets installed (regardless of the feature state of Feature2). Is this the
Well, i tried another scenario as well:
comp1 &Feature2 = 3
where comp1 is in Feature1. Now, i was expecting that comp1 will get
installed if Feature2 is selected for installation. But comp1 NEVER gets
installed (even when Feature2 is selected).
I'm not sure if i'm understanding the concept of how this works well enough.
Can someone please explain the expected behavior for these conditions? FWIW,
these conditions are set at design-time and not through custom actions, so i
don't think they are in the wrong spot in the sequence.
Any help on this would be much appreciated.
Posted 28 July 2005 - 14:08
Posted 28 July 2005 - 18:02
I want to install some components (around 60 components are there that contain only registry entries) from Feature1 but only when Feature2 is removed using Modify option from Add/Remove Programs. And if Feature2 is installed back again
from Add/Remove programs, i want these components in Feature1 to get
re-evaluated and uninstalled. How can i achieve this? It seems like its not
possible at all to use component condition for this. I can write custom
action but these components are generated dynamically (using Installshield automation) so custom action doesn't seem like a good solution to me.
Any help on this would be greatly appreciated!
Edited by rbrinda, 28 July 2005 - 18:13.
Posted 28 July 2005 - 20:31
Anyway you cannot use Component Conditions here. You could move the component to a hidden feature, and select/remove that feature after showing the feature tree.
Posted 28 July 2005 - 21:09
Thanks for your help,