Any suggestions???
On Tue, May 15, 2012 at 11:49 AM, Ravi Raj wrote:
> I have done this thing:
>
> Id="CA_SetProperty_EV" Property="ENABLEVIRTUALIZATION" Value="0"
> Execute="firstSequence" />
> Before="AppSearch">NOT Installed AND NOT
> OLDERVERSIONDETECTED
> NOT Installed AND NOT
> OL
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
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 discuss
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 0x80
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:
http://schemas.microsoft.com/developer/msbuild/2003";>
*Debug
x86
*
This doesn't seem to
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] light.e
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 f
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 tha
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/
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
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]
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
dependencie
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 to
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.
Can anyone help me to do this.
--
Warm Regards
Vivek Soni
vivek.s...@brisetech.com
+91-7877127178
I think what you need to add is "-var var.SourceFiles"; from the help file:
-var
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 File/@Source="!(wix.MySource
15 matches
Mail list logo
