With someone's help, I figured out the approach.
After CostFinalize action, before InstallValidate action, add a customer
action, say UpdateFeatureChange, which changes the feature's reqire state
accordingly.
In DTF, it is as simple as
FeatureInfo featureA2= this.Session.Features["FeatureA2"];
fea
Echo on the question.
I have exactly the same problem:
In my product V1.0, I have
FeatureCommon (always be installed)
Common.dll
FeatureA (optional)
A1.dll
FeatureB (optional)
B1.dll
In my product V1.1 I added A2.dll to feature A
Further to my original question, I have been doing some testing. If find that:
(1) if the patch contains a _new_ file that belongs to a feature that the is
not installed on the user machine, then the patch effectively installs the
feature (and uninstalling the patch does not remove the feature)
3 matches
Mail list logo
