Jason Rivers wrote: > for instance, we always want it to read "[INSTALLDIR]" but if Feature > 1 is installed, then they key should be > "[INSTALLDIR];[INSTALLDIR]\feature1" again, if Feature2 is installed > it should be "[INSTALLDIR];[INSTALLDIR]\feature2" and then if both 1 > and 2 are installed it should read > "[INSTALLDIR];[INSTALLDIR]\feature1;[INSTALLDIR]\feature2" > > is this possible to do? we're currently using a custom action to do > this, but it's messy and it means the string isn't removed on > uninstall unless we have a custom action to do that too.
That's bad karma.<g> The Environment/@Part attribute lets you append or prepend values. I'd use three Environment elements in three components: one that's included in any/all features, one in Feature1, and one in Feature2. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
