Re: [WiX-users] Directory and Registry Search failing in silent mode

2011-12-02 Thread Parkes, Kevin
Log shows SourceDir being set at the same time as SOURCEDIR. I tried scheduling ResolveSource before AppSearch but that gave error LGHT0204: ICE27: 'ResolveSource' Action in InstallExecuteSequence table in wrong place -Original Message- Date: Wed, 30 Nov 2011 13:34:01 -0500 From: "Wilso

[WiX-users] AUTO: Kenneth L Resler is out of the office. (returning 12/05/2011)

2011-12-02 Thread Kenneth . Resler
I am out of the office until 12/05/2011. I will be out of the office, with limited email and phone access. Note: This is an automated response to your message "Re: [WiX-users] Directory and Registry Search failing in silent mode" sent on 12/2/2011 3:12:43 AM. This is the only notification yo

[WiX-users] Component GUID * - same for two different builds

2011-12-02 Thread Thomas . Deboben
Hi, I have a problem with an automatic generated GUID. We use "" for our registry component. Now we build two different Versions on two different build systems but get the same GUID generated in both setups. :-( The problem is, that we can install both versions side by side. The registry key c

[WiX-users] ComboBox - display mismatch between value and text

2011-12-02 Thread Thomas . Deboben
Hi, I'm in trouble with a combobox in a custom installer dialog. If I open the combobox I get a list filled with the text strings and the property will be set to the value string when leaving the dialog by pressing the next button. Fin

Re: [WiX-users] Component GUID * - same for two different builds

2011-12-02 Thread David Watson
The keypath is used to generate the guid at compile time, and I assume in your example the registry key is the keypath. Properties in the registry path will only be resolved at runtime which means that the property name is being used for guid generation. Use your $(var.version) to replace the [VE

Re: [WiX-users] Component GUID * - same for two different builds

2011-12-02 Thread Peter Shirtcliffe
The value of VERSION needs to be resolved at build-time, not run-time, otherwise you're going to generate a potentially invalid component. $(var.xxx) is resolved at build-time; [PROPERTY] is resolved at run-time. Shouldn't the registry key have been written as Key="SOFTWARE\ Company\Product\$(var.

[WiX-users] WixStdba

2011-12-02 Thread David L. Beckwith
Is there a way to set the icon of the standard burn application form, maybe a WixStdbaIconSourceFile variable? Or can the form icon use the IconSourceFile icon? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixStdba-tp7055053p7055053.html Sent fro