Bob Arnson wrote: > > You're going to run into problems: Component rules say that you > shouldn't have two of them writing the same key (even with a different > value). The easiest solution is to create a third component that > writes a property value, then use A and B feature action states to set > the property's value. > Ok I did it that way. Only have one component setting the registry key and a property defining the value.
But my problem still remains, I don't really know how to set the value for a property from a SelectionTree. If component A or B will be installed, so the property holds the right value. Someone can help me with the remaining problem? Thanks in advance, Stefan Seifert ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
