Lough, Norman wrote:
> I've tried various ways of detecting whether the user has selected my
> feature - none of which appear to work - The component in which I
> include the condition never gets installed (implying that the condition
> always evaluates to false(?)) though all other components get
If DisableEnable1 is manually set to no or yes then the edit box behaves
as expected (enabled/disabled). I want to be able to set DisableEnable1
depending on whether a Feature has been installed.
I've tried various ways of detecting whether the user has selected
Perfect. I had a feeling I was trying to make something simple into something
complicated J
Jason
From: Mike Dimmick [mailto:[EMAIL PROTECTED]
Sent: Friday, June 29, 2007 3:30 PM
To: Jason Shay; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Conditional Feature installation
The
June 2007 23:16
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditional Feature installation
I'm making a WIX install with 2 features:
FEATURE_A (installs by default)
FEATURE_B (does not install by default)
My "upgrade" scen
I'm making a WIX install with 2 features:
FEATURE_A (installs by default)
FEATURE_B (does not install by default)
My "upgrade" scenario is a new product and package ID for every version. My
desired behavior is that in any upgrade scenario, the default feature set
[EMAIL PROTECTED] wrote:
I'm trying to show one of 2 mutually exclusive features in the
customize dialog based on the value of ALLUSERS.
For some reason, one is always shown, and the other is always hidden,
no matter what I think the value of ALLUSERS is.
Feature conditions are processed
I'm trying to show one of 2 mutually exclusive features in the customize
dialog based on the value of ALLUSERS.
For some reason, one is always shown, and the other is always hidden, no
matter what I think the value of ALLUSERS is.
Additionally, other aspects of the installation that are dependant
Carl Quirion wrote:
> Ok, i found a simple way to do it, im calling CostFinalize on the
> PushButton of my "Next" button, on the serial number form.
I'm not sure that's supported -- CostFinalize is supposed to be paired
with CostInitialize so I'm not sure you can repeatedly call it.
--
sig://b
Those are already managed in my InstallExecuteSequence. No worries there ;)
--
Carl Quirion
[EMAIL PROTECTED]
On 3/2/07, Stefan Pavlik <[EMAIL PROTECTED]> wrote:
Hi...
what about silent (unattended) installation?
Or installation with reduced UI?
msiexec /i Package.msi /qr
regards
Stefan
Hi...
what about silent (unattended) installation?
Or installation with reduced UI?
msiexec /i Package.msi /qr
regards
Stefan
Carl Quirion wrote:
> Ok, i found a simple way to do it, im calling CostFinalize on the
> PushButton of my "Next" button, on the serial number form.
>
> Example:
>
>
Ok, i found a simple way to do it, im calling CostFinalize on the PushButton
of my "Next" button, on the serial number form.
Example:
1
PIDACCEPTED =
"0"
1
[...]
Thanks
--
Carl Quirion
[EMAIL PROTECTED]
On 3/1/07, Carl Quirion <[EMAIL PROTECTED]> wrote:
From my u
From my understanding, CostFinalize is done before any UI is shown...
however my CA validats a serial number entered by the user.
I can't launch my CA before the user enter his serial number, that wouldnt
make any sense, hehe.
Can re-order the sequence so that CostFinalize is only called after th
Carl Quirion wrote:
My FeatureTree shows up and every products are visible, when i was
expecting product3 to be invisible. Whats wrong?
You probably need to sequence your CA before the CostFinalize action;
that's when MSI "queries the Condition table to
determine which features are scheduled
My installer installs our software suite, which is a 4 product suite.
Using a CustomAction DLL, i validate the provided serial number and set
properties that tells me which product can be installed.
I would like to have my feature tree "modified" by that, so that uneligible
products arent showed.
Hi, Erdi:
I think you should add a custom action after clicking "Next" button of
radio button window to "CostFinalize". Just like this:
*1*
1
And I suggest you set "DATABASECHOICE" property default to "NULL" or
something you like, but don't set it to "MySQL" or "ORACLE". Becuase
whe
erdi wrote:
> The situation is oposite when I declare the DATABASECHOICE property this
> way:
> ORACLE,
> then the OracleSupport feature is installed when picked in radio button
> group and MySqlSupport isn't installed even if picked.
>
Generate a verbose log and check out the feature states d
This problem was mentioned few days ago in this list, but the solution
presented doesn't work for me.
I need to get user decision about what database type (oracle or mysql) is he
going to use with my program. So I made a dialog with radio buttons just
like in point 8.7 of tutorial at http://www
17 matches
Mail list logo
