Writing documentation required a depth of knowledge which I don't presently
have. The WiX documentation suffers from presuming the user already has a
deep understanding.
Take a look at "Fundamental Tools and Concepts". There's NOTHING there!
No concepts at all! It's nothing more than a list of
Actually, I was able to do a web search and find a Very Old example of how
to handle upgrades which actually described what why each XML clause was
needed, and what it did. To bad the so-called documentation doesn't do
that!
I'll show what I came up with for the Basic case, so far.
> installed type (Lite/Basic/Premium) and LaunchCondition will check it and
> prevent unwanted downgrades. Or maybe file search to search for specific
> file that does not exist in higher versions.
>
>
>
> -Original Message-
> From: Tad Carlucci [mailto:tad.carlu...@gm
Can someone point me in the direction to reach this goal:
My requirement is for three flavors of the application: Lite, Basic, and
Premium; each released as a separate MSI package.
The user can only move up the chain. For example, if the Basic is
installed, Lite cannot be installed. If, in the
4 matches
Mail list logo
