Re: [WiX-users] Conditional Feature

[Bob Arnson]

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 installed.
>   

See 
http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditions/. 


-- 
sig://boB
http://joyofsetup.com/



--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditional Feature

[Lough, Norman]

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 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 installed.
I've tried:

 

SampleFeature=3

 

 



 



 

 



 

 

Anyone got an idea where I'm going wrong? Also Once I've established the
right condition what would be the syntax for re-setting the
DisableEnable1 value? Would this typically be done within a Custom
Action?

 

Norman Lough

Developer

Tel: +44 (0)191 213 

DDI: +44 (0)191 2028360

Email: norman.lo...@imass.co.uk

Imass Ltd, Northumbria House, Regent Centre, Gosforth, Newcastle upon
Tyne, NE3 3PX. http://www.imass.co.uk  

 

Imass Limited is an Infoterra company, part of EADS Astrium

 

 

Registered in England and Wales No. 2379476

 

- Disclaimer -
The information contained in this e-mail and its attachments is
confidential and intended only for the use of the individual or entity
named above.  If you are not the intended recipient, please do not read,
copy, use or disclose this message or its attachments.  If you have
received this message in error, please notify the sender immediately and
delete or destroy all copies of this message and attachments in all
media.  Any views expressed in this e-mail that do not relate to Imass'
official business may not reflect the views of the company.

 

--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional Feature installation

[Jason Shay]

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 MigrateFeatureStates action is supposed to do that for you. Set 
UpgradeVersion/@MigrateFeatureStatus to 'yes' on the versions you want the 
migration to happen for.

--
Mike Dimmick


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Shay
Sent: 29 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" scenario is a new product and package ID for every version.  My 
desired behavior is that in any upgrade scenario, the default feature set stays 
consistent with what is already installed, and not to snap back to the "new 
user defaults".

In other words:

1)  User installs and via UI, only installs FEATURE_B (goes against both 
defaults)

2)  User gets next version, runs MSI to upgrade.  I want the installer to 
detect what is installed, and have the default selected feature set to be only 
FEATURE_B.

I was thinking of doing this by putting a condition in the feature tag to 
change the level when a feature is installed.  But documentation says that 
won't work because the enumeration of which features are installed happens too 
late in the process.   Any suggestions?

I'm on WIX v2, BTW.

Jason
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional Feature installation

[Mike Dimmick]

The MigrateFeatureStates action is supposed to do that for you. Set
UpgradeVersion/@MigrateFeatureStatus to 'yes' on the versions you want the
migration to happen for.

 

-- 

Mike Dimmick

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason Shay
Sent: 29 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" scenario is a new product and package ID for every version.  My
desired behavior is that in any upgrade scenario, the default feature set
stays consistent with what is already installed, and not to snap back to the
"new user defaults".  

 

In other words:

1)  User installs and via UI, only installs FEATURE_B (goes against both
defaults)

2)  User gets next version, runs MSI to upgrade.  I want the installer
to detect what is installed, and have the default selected feature set to be
only FEATURE_B.

 

I was thinking of doing this by putting a condition in the feature tag to
change the level when a feature is installed.  But documentation says that
won't work because the enumeration of which features are installed happens
too late in the process.   Any suggestions?

 

I'm on WIX v2, BTW.

 

Jason

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditional Feature installation

[Jason Shay]

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 stays 
consistent with what is already installed, and not to snap back to the "new 
user defaults".

In other words:

1)  User installs and via UI, only installs FEATURE_B (goes against both 
defaults)

2)  User gets next version, runs MSI to upgrade.  I want the installer to 
detect what is installed, and have the default selected feature set to be only 
FEATURE_B.

I was thinking of doing this by putting a condition in the feature tag to 
change the level when a feature is installed.  But documentation says that 
won't work because the enumeration of which features are installed happens too 
late in the process.   Any suggestions?

I'm on WIX v2, BTW.

Jason
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature install

[Bob Arnson]

[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 by the CostFinalize action, which 
happens before UI is shown. If you want the UI to control feature 
selection, you need to use the AddLocal and/or Remove control events in 
your feature-selection dialog.


--
sig://boB
http://bobs.org

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditional feature install

[Chris.Rowland]

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 on
the ALLUSERS property are working fine

 

I've defined my Features like so:

 

 







ALLUSERS



 







NOT ALLUSERS



 

Feat_WorkDirectoryAll is always displayed in the Customize dialog, and
the other feature never is.  I've looked in the log to verify ALLUSERS
and the appearance of the Customize dialog is the same in either case (1
or nothing).

 

I'm setting the ALLUSERS property with a CA a few dialogs earlier but in
the single user case it's null.  .

 

 

Is there an error in my Condition logic?

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature properties...

[Bob Arnson]

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://boB
http://bobs.org



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature properties...

[Carl Quirion]

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


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:
>
>  Height="17" Default="yes" Text="&Next">
>   1
>   PIDACCEPTED
> = "0"
>   1
> [...]
>
> Thanks
>
> --
> Carl Quirion
> [EMAIL PROTECTED] 
>
> On 3/1/07, *Carl Quirion* <[EMAIL PROTECTED] >
> wrote:
>
> >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
> that particular dialog (Before the feature tree dialog) ?
>
>
> On 3/1/07, *Bob Arnson* <[EMAIL PROTECTED] > 
wrote:
>
> 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 to be installed" (or so says the doc).
>
> --
> sig://boB
> http://bobs.org
>
>
>
>
>
> --
> Carl Quirion
> [EMAIL PROTECTED] 
>
>
>
>
>
> 
>
>
-
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
your
> opinions on IT & business topics through brief surveys-and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
>
> 
>
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies s.r.o. | www.whitestein.com
Panenska 28 | 811 03 Bratislava | Slovak Republic
Main +421 2 5443-5502 | Direct +421 2 5930-0735

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature properties...

[Stefan Pavlik]

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:
> 
>  Height="17" Default="yes" Text="&Next">
>   1
>   PIDACCEPTED
> = "0"
>   1
> [...]
> 
> Thanks
> 
> -- 
> Carl Quirion
> [EMAIL PROTECTED] 
> 
> On 3/1/07, *Carl Quirion* <[EMAIL PROTECTED] >
> wrote:
> 
> >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
> that particular dialog (Before the feature tree dialog) ?
> 
> 
> On 3/1/07, *Bob Arnson* <[EMAIL PROTECTED] > 
> wrote:
> 
> 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 to be installed" (or so says the doc).
> 
> -- 
> sig://boB
> http://bobs.org
> 
> 
> 
> 
> 
> -- 
> Carl Quirion
> [EMAIL PROTECTED] 
> 
> 
> 
> 
> 
> 
> 
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> 
> 
> 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

-- 
Stefan Pavlik | [EMAIL PROTECTED]
Whitestein Technologies s.r.o. | www.whitestein.com
Panenska 28 | 811 03 Bratislava | Slovak Republic
Main +421 2 5443-5502 | Direct +421 2 5930-0735

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature properties...

[Carl Quirion]

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 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 that
particular dialog (Before the feature tree dialog) ?

On 3/1/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
>
>  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 to be installed" (or so says
> the doc).
>
> --
> sig://boB
> http://bobs.org
>
>
>


--
Carl Quirion
[EMAIL PROTECTED]

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature properties...

[Carl Quirion]

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 that
particular dialog (Before the feature tree dialog) ?

On 3/1/07, Bob Arnson <[EMAIL PROTECTED]> wrote:


 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 to be installed" (or so says the
doc).

--
sig://boB
http://bobs.org






--
Carl Quirion
[EMAIL PROTECTED]
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature properties...

[Bob Arnson]

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 to be installed" (or so says the 
doc).


--
sig://boB
http://bobs.org


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditional feature properties...

[Carl Quirion]

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.

Here's my features:
   
 

 
   PRODUCT1 = "0"
   
 
 
   PRODUCT2 = "0"
   
 
 
   PRODUCT3 = "0"
   
 
 
   PRODUCT4 = "0"
   
 
   

When i launch my MSI with loggin enabled, i see my properties getting setted
properly by my CustomAction
MSI (c) (FC!90) [10:15:12:557]: PROPERTY CHANGE: Adding PIDACCEPTED
property. Its value is '1'.
MSI (c) (FC!90) [10:15:12:557]: PROPERTY CHANGE: Adding PRODUCT1 property.
Its value is '1'.
MSI (c) (FC!90) [10:15:12:557]: PROPERTY CHANGE: Adding PRODUCT2 property.
Its value is '1'.
MSI (c) (FC!90) [10:15:12:557]: PROPERTY CHANGE: Adding PRODUCT3 property.
Its value is '0'.
MSI (c) (FC!90) [10:15:12:557]: PROPERTY CHANGE: Adding PRODUCT4 property.
Its value is '1'.

After that i get
Action 10:15:12 : CustomizeDlg. Dialog created

My FeatureTree shows up and every products are visible, when i was expecting
product3 to be invisible. Whats wrong?

For reference, im using WixUI_Mondo source as a template and have some
modifications done in it. I dont think that changes anything, just letting
you know.

Thanks!
--
Carl Quirion
[EMAIL PROTECTED]
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature installation problem

[Liu Qian]

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 
when msi execute your package and do "CostFinalize" automatically, it 
will check the condition of features. So I suggest you set property to 
"NULL" to ensure two of features are selected when installation begin.

You can find more information here: 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/costfinalize_action.asp.
 
Basically, when you change the feature or components you want to 
install, you need run "CostFinalize" again.

L.Q.

erdi wrote:
> 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.tramontana.co.hu/wix/ and 
> inserted it into the WiX UI library like in point 2.5 of the same tutorial.
>
> The property connected with radio buttons is declared this way:
>
> MySQL
>
> so it's both public and registered under SecureCustomProperties property - 
> I've also checked it in Orca to be sure.
>
> the radio buttons are declared this way:
>
> 
>  Value="MySQL" X="5" Y="0" Width="250" Height="15" />
>  Value="ORACLE" X="5" Y="20" Width="250" Height="15" />
> 
>
> and the conditional features are:
>
> 
>NOT (DATABASECHOICE = "MySQL")
>
>
>
>   
>   
>NOT (DATABASECHOICE = "ORACLE")
>
>
>   
>
> Now, when I start the installer and leave the property default, not changing 
> the selection in radio button group everything works fine - the MySqlSupport 
> feature
> is installed correctly. When I pick the Oracle database from the radio 
> button group then OracleSupport feature isn't installed. But what's very 
> interesting in the log file i can find such lines:
> Property(S): DATABASECHOICE = ORACLE
> Property(C): DATABASECHOICE = ORACLE
> PublishFeatures: Feature: OracleSupport,
> so the property seems to be set corectly.
>
> 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.
>
> Please help, I've been fighting with this for last two days and I'm 
> desperate now
>
> Erdi
>
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>   


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Conditional feature installation problem

[Bob Arnson]

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 described around 
the InstallValidate action. They'll tell you what MSI's installing. Then 
check the log for "PROPERTY CHANGE" messages.

Also, you might want to consider an opposite approach. Rather than 
installing both by default and disabling one, install neither by default 
(level 0) and enable the one the user chooses.

-- 
sig://boB
http://bobs.org


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Conditional feature installation problem

[erdi]

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.tramontana.co.hu/wix/ and 
inserted it into the WiX UI library like in point 2.5 of the same tutorial.

The property connected with radio buttons is declared this way:

MySQL

so it's both public and registered under SecureCustomProperties property - 
I've also checked it in Orca to be sure.

the radio buttons are declared this way:






and the conditional features are:


   NOT (DATABASECHOICE = "MySQL")
   
   
   
  
  
   NOT (DATABASECHOICE = "ORACLE")
   
   
  

Now, when I start the installer and leave the property default, not changing 
the selection in radio button group everything works fine - the MySqlSupport 
feature
is installed correctly. When I pick the Oracle database from the radio 
button group then OracleSupport feature isn't installed. But what's very 
interesting in the log file i can find such lines:
Property(S): DATABASECHOICE = ORACLE
Property(C): DATABASECHOICE = ORACLE
PublishFeatures: Feature: OracleSupport,
so the property seems to be set corectly.

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.

Please help, I've been fighting with this for last two days and I'm 
desperate now

Erdi


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users