My project gets/sets some Properties from a user entered Registration Code all handled within a VBScript action which follows Cost Finalize. The properties are then used as conditions to install various files. For example, the entered registration code is parsed to indicate that a Property, lets say, COMPANY = ABDG.
I previously placed the condition COMPANY = ABDG on any component that should be installed specific to that company. This seemed to work on NT & 2K, but not 9X.
I consulted the IS Know. Base which indicated to do the following: Cut the condition from the component, create a subfeature (which in essence contains/is the component) with an Install Level higher than the project's. The install level is set to lower than the project's if the original condition evaluates to True. Then, as a control event, I used AddLocal/Feature/Same Condition.
I used the AddLocal with the behavior of the Install button on the Ready to Install dialog which occurs immediately after the Registration Code VBScript.
Is this OK? Am I missing something?
My install still seems to be ignoring the conditions and dumps all files to the target.
I hope this is clear, but I doubt it! MUCH Thanks!!!
(Edited by Superfreak3 at 5:04 pm on Aug. 29, 2001)