Re: [WiX-users] building an msi in the same dir as source files?

2012-05-18 Thread Neil Sleightholm
I think what you need to add is -var var.SourceFiles; from the help file: -var VariableName Substitute File/@Source=SourceDir with a preprocessor or a wix variable (e.g. -var var.MySource will become File/@Source=$(var.MySource)\myfile.txt and -var wix.MySource will become

[WiX-users] Launch an msi after installation

2012-05-18 Thread Vivek Soni
Hello, I created a wix installer in which I want to launch an msi after installation. I was trying using following code but it's not working. CustomAction Id=StartAppOnExit FileKey=Dlg_Setup.msi ExeCommand=param1 Execute=immediate Return=asyncNoWait / InstallExecuteSequence Custom

Re: [WiX-users] Launch an msi after installation

2012-05-18 Thread Richard Mayes
Firstly to launch an msi you would need to use msiexec ( http://support.microsoft.com/kb/227091) you cannot call an msi directly as it is not an executable. However in your case this will not be possible as you are in a msi transaction already and won't be able to start a new one. You will need

Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64

2012-05-18 Thread Gareth
But you can install 64-bit dlls withoin a 32-bit package - they're just files. So, we add a dll that allows the 64-bit operating system to interogate our bespoke document formats in order to draw pretty thumbnail previews. But this code only works if the operating sytem has the required

Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64

2012-05-18 Thread Daniel Madill
Hi Gareth, I install 32-bit applications in a 64-bit installer all the time. I use the Win64=no attribute on the 32-bit registry entries to ensure they go in the 32-bit hive on the 64-bit platform. Sincerely, Daniel Madill -Original Message- From: Gareth [mailto:gmor...@serif.com]

Re: [WiX-users] service uninstall fails if ServiceControl does not specify install= ???

2012-05-18 Thread Bob Arnson
On 17-May-12 20:20, Dave Combs wrote: MSI (s) (9C:24) [17:03:39:948]: Component: CMP_162; Installed: Local; Request: Absent; Action: Null That usually indicates something else, expressed earlier in the log, is preventing the requested action, such as violating the component rules. Try it in

Re: [WiX-users] Specifying source subdirectory

2012-05-18 Thread Bob Arnson
On 16-May-12 12:52, Martin Sustrik wrote: C:\Users\me\libxs\foo.wxs(98) : error LGHT0103 : The system cannot find the file 'foo.h'. See How To: Specify source files in wix.chm. -- sig://boB http://joyofsetup.com/ --

Re: [WiX-users] MSI projects fail to build after upgrading to v3.6.2914.0

2012-05-18 Thread Bob Arnson
On 16-May-12 05:28, Pally Sandher wrote: Just don't need them. Never got around to using WiX only for patching so I don't see any use for them. There's nothing in WiX today that needs them, other than patching, but that might change; there's lots of good info that's pre-digested in a way that

Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64

2012-05-18 Thread Bob Arnson
On 18-May-12 11:32, Gareth wrote: But you can install 64-bit dlls withoin a 32-bit package - they're just files. Not if they're marked as a 64-bit component that goes into a 64-bit part of the file system. Then they're special. then how can a 64-bit operating system interogate a bespoke file

Re: [WiX-users] light.exe error when merging VC100 merge modules for both x86 and x64

2012-05-18 Thread Wilson, Phil
Just to add the doc link: http://msdn.microsoft.com/en-us/library/windows/desktop/aa367451(v=vs.85).aspx Phil W From: Bob Arnson [b...@joyofsetup.com] Sent: Friday, May 18, 2012 9:13 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users]

[WiX-users] In .wixproj, default Build Configuration ignored or not settable?

2012-05-18 Thread john.burak
It's my understanding that with MSBuild, the configuration and platform used when none are specified is defined near the top of the project file in the elements with blank conditions, like this: ?xml version=1.0 encoding=utf-8? Project ToolsVersion=4.0 DefaultTargets=Build

[WiX-users] Error when doing a REG_MULTI_SZ registry search within Burn.

2012-05-18 Thread Richard Mayes
Hi I've been trying to bootstrap Sql 2008 Express and install if required however my detection Registry search is failing with the following error: Error 0x80004001: Unsupported registry key value type. Type = '7' RegistrySearchValue failed: 'SOFTWARE\Microsoft\Microsoft SQL Server', HRESULT

Re: [WiX-users] Error when doing a REG_MULTI_SZ registry search within Burn.

2012-05-18 Thread Neil Sleightholm
I believe you need to set the attribute RegistrySearch/@Type=raw to read REG_MULTI_SZ values, see http://wix.sourceforge.net/manual-wix2/wix_xsd_registrysearch.htm Neil -Original Message- From: Richard Mayes [mailto:caveman.d...@gmail.com] Sent: 18 May 2012 20:54 To: General

Re: [WiX-users] Error when doing a REG_MULTI_SZ registry search within Burn.

2012-05-18 Thread Bob Arnson
On 18-May-12 15:53, Richard Mayes wrote: Error 0x80004001: Unsupported registry key value type. Type = '7' RegistrySearchValue failed: 'SOFTWARE\Microsoft\Microsoft SQL Server', HRESULT 0x8000400 Like MSI, Burn doesn't support getting the value of a multi-sz string. However, if all you want to

Re: [WiX-users] CheckBox Value via Custom Action

2012-05-18 Thread Ravi Raj
Any suggestions??? On Tue, May 15, 2012 at 11:49 AM, Ravi Raj raviraj.callin...@gmail.comwrote: I have done this thing: Property Id=ENABLEVIRTUALIZATION Secure=yes /CustomAction Id=CA_SetProperty_EV Property=ENABLEVIRTUALIZATION Value=0 Execute=firstSequence / InstallExecuteSequence