Re: [WiX-users] LGHT0091: Duplicate symbol error

2015-01-14 Thread Nick Ramirez
I tried something similar and it compiled okay for me. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LGHT0091-Duplicate-symbol-error-tp7598838p7598856.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] LaunchConditions on a REG_DWORD returned from a RegistrySearch

2015-01-14 Thread roberthyang
You can do string comparisons, eg. REGVAL = #12300 but of course it will be a bit brittle. If your expected values are say, 11200 through 9 then it's probably fine, but once it reaches 10 then there will be problems :) Kevin Palmer wrote Hi, I've searched and cannot find a suitable

[WiX-users] App1 to launch an App2 (with advertised shortcut, not installed yet)

2015-01-14 Thread Phill Hogland
I have amsi which installs a single app with an advertised shortcut in the Start menu. After the MSI is installed, until the user clicks on the advertised shortcut, the exe is not yet installed yet. I have a c++/Win32 developer who plans to add code to his app to launch this exe as a child

Re: [WiX-users] Modifying a MSPs contents

2015-01-14 Thread Bob Arnson
On 13-Jan-15 14:35, Tunney, Stephen wrote: Rob, Bob, et al, is there any dark magic out there that can assist in this quest? No. DTF can read a lot and write a bit. Reassembling packages isn't on the todo list for either DTF or Wix.dll. -- sig://boB http://joyofsetup.com/

Re: [WiX-users] Two Mutually Exclusive Products

2015-01-14 Thread John Cooper
Because PROPERTY implies the property exists but has no value, but with the Windows Installer Service, the property will be removed if it is empty. Hence, NOT PROPERTY is the test that should be used. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications |

Re: [WiX-users] LaunchConditions on a REG_DWORD returned from a RegistrySearch

2015-01-14 Thread Phill Hogland
IF using a bundle, use util:RegistrySearch Format=raw and pass the result as a property to the MSI (or handle the launch condition in the ba). From what I have read, if using a msi only, then I think you need the CA. -- View this message in context:

Re: [WiX-users] Two Mutually Exclusive Products

2015-01-14 Thread Marc Beaudry
I have a simple condition question: I have my installer working as I need but I need clarification on something, and yes I fully understand this is of the most basic understanding, but it doesn't match what I am reading (probably misunderstanding) in documentation. My WIX Code: Property

Re: [WiX-users] Two Mutually Exclusive Products

2015-01-14 Thread Marc Beaudry
Thanks for the VERY CLEAR explanation... I understand what's happening and why... -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: January-14-2015 12:39 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Two Mutually Exclusive Products

[WiX-users] Add manifest to a bundle

2015-01-14 Thread Martin Johnson
Following on from some work a colleague commenced I need to add a manifest to a bundle to pass the microsoft platform test, the following had been added to Wix2010.targets Target Name=PatchSetupExe Exec Command='C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\mt.exe -nologo