Stefan Seifert wrote:
> 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.
>
You need to set the property, such as with a custom action. You can use
th
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 s
Stefan Seifert wrote:
> I have a component A which has a Registry Key (lets call it: A.Registry)
> with a value and I got a component B which has the same Registry Key
> with a different value (lets call it: B.Registry).
>
You're going to run into problems: Component rules say that you
shouldn
3 matches
Mail list logo
