I have 2 merge modules. Dependent of a property I want to include the one or
the other merge module. By the moment I have this solved via separate features
combined with a condition:
<Feature Id="ProductFeature" Title="Complete" Level="1">
<Feature Id="MergeA" Title="MergeA" Level="1">
<Condition Level="0">NOT Property="Value"</Condition>
<MergeRef Id="..." />
</Feature>
...
</Feature>
In the merge module I have custom actions included. Theses custom actions get
executed during install even if the feature (and so the merge module) is
disabled. My workaround is to use the feature condition property also for the
custom action condition:
<Custom Action="..." After="...">NOT Installed AND Property="Value"</Custom>
This works, but it is very boring because I have a lot of custom actions. And I
think there must be a more elegant way to solve this issue. But which?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
