Re: [WiX-users] Control conditional on installed components

2009-02-08 Thread Chris Ridd
On 8 Feb 2009, at 18:22, Bob Arnson wrote: > Chris Ridd wrote: >> Is the ?component notation in control conditions supported by all >> versions of Windows Installer? > > Yes, but it might not work when you cross from the UI to the execute > and > back to the UI. There's no doc to say either way

Re: [WiX-users] Control conditional on installed components

2009-02-08 Thread Bob Arnson
Chris Ridd wrote: > Is the ?component notation in control conditions supported by all > versions of Windows Installer? Yes, but it might not work when you cross from the UI to the execute and back to the UI. There's no doc to say either way. I'd suggest replicating the conditions rather than

Re: [WiX-users] Control conditional on installed components

2009-02-08 Thread Chris Ridd
On 8 Feb 2009, at 01:33, Rob Mensching wrote: > Not sure. Have you tried following the Property value changes in > the verbose log file to make sure it ends up what you want? I'm seeing lines like: AppSearch: Property: JDK15HOME, Signature: S_JDKHOME15 MSI (c) (74:D4) [13:19:54:468]: Note: 1

Re: [WiX-users] Control conditional on installed components

2009-02-07 Thread Rob Mensching
. Subject: Re: [WiX-users] Control conditional on installed components On 6 Feb 2009, at 21:47, Rob Mensching wrote: > The __Components are MSI things (for costing, IIRC). You can ignore > them. OK. I double-checked my WXS and they weren't there. > The registry key path/name/value

Re: [WiX-users] Control conditional on installed components

2009-02-06 Thread Chris Ridd
On 6 Feb 2009, at 21:47, Rob Mensching wrote: > The __Components are MSI things (for costing, IIRC). You can ignore > them. OK. I double-checked my WXS and they weren't there. > The registry key path/name/value should not be case sensitive but > whenever referring to an Id in the MSI you s

Re: [WiX-users] Control conditional on installed components

2009-02-06 Thread Rob Mensching
Ridd [mailto:chrisr...@mac.com] Sent: Friday, February 06, 2009 05:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Control conditional on installed components On 5 Feb 2009, at 18:36, Rob Mensching wrote: > You need the "*v" to get it all. I

Re: [WiX-users] Control conditional on installed components

2009-02-06 Thread Chris Ridd
On 5 Feb 2009, at 18:36, Rob Mensching wrote: > You need the "*v" to get it all. I never bother with logs any other > way. Nothing else (except the MSI itself to cross reference) is > usually necessary. OK, I now have verbose logs of an install with Java and without Java. I'm eliding all

Re: [WiX-users] Control conditional on installed components

2009-02-05 Thread Rob Mensching
ussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Control conditional on installed components On 5 Feb 2009, at 17:54, Rob Mensching wrote: > Verbose log file should show you the states of everything. I didn't see anything in the logs earlier, but then I didn't use

Re: [WiX-users] Control conditional on installed components

2009-02-05 Thread Chris Ridd
On 5 Feb 2009, at 17:54, Rob Mensching wrote: > Verbose log file should show you the states of everything. I didn't see anything in the logs earlier, but then I didn't use /l*v. Will try again tomorrow! Do the component installation states get recorded automatically, or do I need to arrange

Re: [WiX-users] Control conditional on installed components

2009-02-05 Thread Rob Mensching
Verbose log file should show you the states of everything. -Original Message- From: Chris Ridd [mailto:chrisr...@mac.com] Sent: Thursday, February 05, 2009 09:51 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Control conditional on installed components I've been bashi

[WiX-users] Control conditional on installed components

2009-02-05 Thread Chris Ridd
I've been bashing my head against this all day today :-( We optionally install some shortcuts to things written in Java, and I want to warn in the ExitDialog if those shortcuts were wanted but could not be installed because Java's not there. To add complexity, we allow the user to use differ