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
ation)?
Thanks
sanjay
> -Original Message-
> From: Sanjay Poria [mailto:sanjay.po...@xanalys.com]
> Sent: 05 February 2012 21:21
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: [WiX-users] Patching and Pyro Warning PYRO1110
>
> I have cr
I have created an MSI product installer for a product that has a main feature
(call it MF) and a sub feature (call it SF). It is mandatory to install the
main feature but the sub feature is optional.
I am experimenting with creating patches (small updates) using Wix 3.5 for this
product. I hav
4 matches
Mail list logo
