Scratch that question and thanks for the reminder/redirection to the msi
provided addlocal functionality. From past experience with other installers I
recall that addlocal=featureFoo,featureBar sets the feature action choice
versus my public property approach I've been using to conditionally
Condition on a Feature? In case you conditionally wanted a Feature to show up
in the tree or not.
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 14:36
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re:
I see so the reason for feature conditions that would adjust level from 0
enabled to 0 disabled would be something like if you wanted to automatically
check for a version specific prerequisite and if not present automatically
disable that feature option. Do any of the WIXUI_* provided
No, IIRC the MSI SDK says 0 == disabled/absented/invisibled/like no longer
seen, dude.
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 15:51
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] correct
I have the following logic in each of my feature/subfeature settings so that
from the command line users can easily define what features/subfeatures are
selected and unselected by default when they step into the interactive install
or run and unattended install.
When I run my msi in
MSI also has ways of controlling features using ADDLOCAL and friends. That
might work better...
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 14:05
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users]
6 matches
Mail list logo