Hello Don, It's too late to change feature list at that time (GUI part of install). Asign Level attribute for your LoggingFeature and in publish events set INSTALLLEVEL property to value above or below the Level attribute of your feature to control whether it should be installed or not. Something like that :)
Friday, May 25, 2007, 3:23:15 PM, you wrote: > I have the following 2 commands inside a “next” button control: > > <Publish Event="Remove" > Value="LoggingFeature">PROPERTY1="1" OR PROPERTY2="1"</Publish> > <Publish Event="AddLocal" > Value="LoggingFeature">PROPERTY1="0" AND PROPERTY2="0"</Publish> > > But instead of adding and removing the feature “LoggingFeature” I > end up with 2 properties REMOVE and ADDLOCAL > > REMOVE ends up equaling “LoggingFeature” > ADDLOCAL ends up equaling a comma deliminated list of all my features. > > When I comment out these two lines everything seems to work fine > (except for the functionality I’m trying to achieve). > > Any ideas? -- Best regards, Alexei Boukirev ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
