Ultimately I am controlling what the user sees, the stripping out of the
merge modules is simply reducing the size of the package. Using the
condition table I have a consistent feature table for all packages, and
encapsulate exclusions within each package.
Probably FeatureGroups will work, but a
The Condition table is designed for enabling/disabling which features get
installed at install-time. It sounds like your intent is to control which
features get included into your various MSIs at build-time. For your
situation the use of shared install code would enable you to have a similar
set
Mike,
Basically I need to adjust the feature tree for each MSI.
Each of the 10 MSIs is a distinct product package with a unique upgrade
code. Payload is attached to features via mergemodules. If the feature tree
contains features A and B, with sub-features A0 - An, B0 - Bn, the first MSI
could
I'm not sure I follow exactly what you'd like to accomplish. WiX has a lot
of tools for sharing installation code between projects and conditionally
including setup logic with preprocessor variables, etc. I'm confident
you'll be able to accomplish what you want with WiX.
The Condition table is
I am in the process of attempting to migrate several (10) installs from Wise
to Wix and have come across an issue I am not certain how best to deal with.
Nine of the installs are branded versions of the first, each of which only
differs slightly from the main install. In Wise I used the condition t
5 matches
Mail list logo
