Sent: December-19-12 12:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and condition message in installer
Wouldn't your x86 search need to search the WoW6432Node of HKLM to be correct?
HKLM:\Software\Wow6432Node\Microsoft\Windows\Curre
12 9:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and condition message in
installer
That would only work at build time, if you were compiling an x86 MSI and
an x64 MSI.
I think you just need to extend your condition to something
: [WiX-users] Registry search and condition message in installer
Glad it works for you. To explain the logic, it's adding a clause to each
condition so that it will resolve to true if you're on the
*other* architecture. So:
Installed OR (SQLSYNCX64SEARCH > "0" AND VersionNT
elp... the below from John works like a charm!
> Can't get my head around the logic but it works...
>
> Steve
>
> -Original Message-
> From: John Ludlow [mailto:john.ludlow...@gmail.com]
> Sent: December-19-12 9:24 AM
> To: General discussion for Windows Installer XML to
ndows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and condition message in installer
That would only work at build time, if you were compiling an x86 MSI and an x64
MSI.
I think you just need to extend your condition to something like this:
Installed OR (SQLSYNCX64SEARCH >
cember-19-12 5:11 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Registry search and condition message in installer
>
> VersionNT64 is undefined on a 32-bit OS so Installed OR (SQLSYNCX64SEARCH >
> "0" AND VersionNT64) would be
&g
Then I will have to use $(var.Platform) <> "x86" that should work
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: December-19-12 5:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and c
December 2012 04:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and condition message in installer
Oops I should have said as well...
The 32 bit version is checked and correct since it is installed so the logic
is correct for the 32 bit check
Sent: December-18-12 7:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and condition message in installer
I always use a verbose log file to check the values of Properties since that
where I usually make my mistakes.
On Tue, Dec 18, 2012 at 3:
er-18-12 7:19 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry search and condition message in installer
I always use a verbose log file to check the values of Properties since that
where I usually make my mistakes.
On Tue, Dec 18, 2012 at 3:
I always use a verbose log file to check the values of Properties since
that where I usually make my mistakes.
On Tue, Dec 18, 2012 at 3:14 PM, StevenOgilvie wrote:
> I have a 32 bit installer, it can run on a 32 bit or a 64 bit OS...
> On the 32 bit OS only the 32 bit pre requisites are run, b
I have a 32 bit installer, it can run on a 32 bit or a 64 bit OS...
On the 32 bit OS only the 32 bit pre requisites are run, but on the 64 bit
OS both 32/64 bit pre requisites are run.
The installer verifies that the pre requisites are installed (ya its
overkill but that is another story)...
On a
RegLocator/AppSearch doesn't support this. You'd have to write a custom
action.
From: "Michael Ogilvie"
Sent: Thursday, October 25, 2012 2:38 PM
To: "General discussion for Windows Installer XML toolset."
Subject: [WiX
Hello,
Does anybody know if you can create a registry search with a wildcard in
the key?
I need to find the Labview install folder but I don't know what version
of Labview they might have.
Key would be something like this: Root="HKLM Key="SOFTWARE\National
Instruments\LabVIEW\12.0" I ne
012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] registry search overridden when "Program Files"
encountered
Here is the situation: I have this application that is available both as
32-bit and 64-bit. Now I'm building an installe
- Helix Building, West Of Scotland Science Park, Glasgow
> G20 0SP
> Email Disclaimer
>
>
> -Original Message-
> From: Marius Bancila [mailto:marius.banc...@gmail.com]
> Sent: 09 February 2012 13:32
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] regis
cotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Marius Bancila [mailto:marius.banc...@gmail.com]
Sent: 09 February 2012 13:32
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] registry
Windows Installer does this be design so you really shouldn't try working
around it. But, see this post for more information:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-allow-32-bit-installer-to-write-to-C-Program-Files-td5544693.html#a5550286
http://windows-installer-xml
Hi,
I have the following problem installing to a path read from the registry.
I'm using WIX 3.5 (and currently testing on a Win7 64-bit).
I'm doing a registry search like this:
Then I use it like this:
If you ever need to read a section of the registry that differs from the
bitness of the process you are executing in you can use this Windows API,
RegQueryValueEx
(http://msdn.microsoft.com/en-us/library/ms724897(v=vs.85).aspx). You can
change the section of the registry being read with the samDes
er
-Original Message-
From: Daetrin Nickname [mailto:gfin...@gmail.com]
Sent: 05 April 2011 01:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registry Search in x86 installers doesn't work
properly on x64 machines
Actually, after a couple hours m
Actually, after a couple hours more searching around i finally
stumbled across this bug report:
http://sourceforge.net/tracker/index.php?func=detail&aid=3013386&group_id=105970&atid=642714
I've spent so many years training myself that "Win64=yes" was for x64
builds and "Win64=no" was for 32-bit b
> Running 32 bit apps in a 32 bit shell is a great idea, but it seems less than
> ideal
> that it excludes all possibility of viewing the registry as it "really" is.
My point is that the operating system provides a 32-bit view for 32-bit
applications since they only know of the 32-bit world. A 3
gt; Sent: Monday, April 04, 2011 3:49 PM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Registry Search in x86 installers doesn't work
>> properly on x64 machines
>>
>> We actually already have two different installers. Howeve
Message-
> From: Daetrin Nickname [mailto:gfin...@gmail.com]
> Sent: Monday, April 04, 2011 3:49 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Registry Search in x86 installers doesn't work
> properly on x64 machines
>
> We a
We actually already have two different installers. However the problem
is that we need to account for the possibility that they've installed
an x64 version of the main program on an x64 machine, and then try to
install the x86 version of the utility on the same machine. So the x86
installer needs t
I believe you need to issue two different installers and set the Win64
attribute for each RegistrySearch element.
You should not specify the Wow3264Node in the path.
If you need to do this in a single installer, you will need to condition the
search so that it only triggers for the appropriate OS
We're trying to do a couple registry searches at the beginning of a
utility installation to check for the existence of our main product so
we can take certain actions. Everything works fine when using the x64
installer on an x64 machine, but when we try the x86 installer all
the registry checks fa
n farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Wednesday, February 17, 2010 11:13 PM
To: 'Blair'
Subject: RE: [WiX-users] Registry search help, and invoking a dialog if a
condition is set
Hi:
Cheers
Show I store the registry element as raw or as a string? What's the
difference?
Cheers
Sean.
-users] Registry search help, and invoking a dialog if a
condition is set
As far as the modification of ini files is concerned, you probably won't
need a custom action. There are some built in elements.
http://wix.sourceforge.net/manual-wix3/wix_xsd_inifile.htm
http://wix.sourceforge.net/manual
As far as the modification of ini files is concerned, you probably won't
need a custom action. There are some built in elements.
http://wix.sourceforge.net/manual-wix3/wix_xsd_inifile.htm
http://wix.sourceforge.net/manual-wix3/wix_xsd_inifilesearch.htm
On Thu, Feb 18, 2010 at 11:13 AM, sean farro
Hi:
I need to search for a registry key, store this in a property and then
execute a dialogue if the property is set. I also need to execute the
found registry key as a custom action, if the yes button is pressed. How
would i go about this.
Also does wix allow the writing of custom ini files, or
.
-Original Message-
From: sean farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Tuesday, February 09, 2010 4:57 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Registry search and showing a message box
Hi:
Thanks, is there a yes/no dialo
February 2010 00:39
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Registry search and showing a message box
You can set properties using the AppSearch-related RegistrySearch.
You can then use those properties in your UI sequence to ask the us
: Tuesday, February 09, 2010 3:29 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Registry search and showing a message box
Hi:
Hi:
I need toperform a registry search for an uninstallation program (this is
an older version). Where should this be
Hi:
Hi:
I need toperform a registry search for an uninstallation program (this is
an older version). Where should this be put, this doesn't need to be a
launch condition in this case.
If the executable exists, I then need to show a message box with yes/no
butons, and run the executable is the
tyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Prabhakaran Paulraj [mailto:prabhakaran_paul...@dynamicbi.com]
Sent: Wednesday, September 30, 2009 13:15
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registry s
Hi,
I am following a registry search condition. This condition is to check if
the SQL Server of version 9.00.4035.00 is installed at the time of
install/repair/change.
This works fine in windows XP Professional, i get this message when SQL
Server of version 9.00.4035.00 is not available
wix-users@lists.sourceforge.net
Subject: [WiX-users] Registry Search Condition Message Wix 2.0
Hi,
I want to continue with the Setup (installation, repair or remove) only if
the following registry key is found.
'Test Folder do not exist'>REGISTRYSEARCH=#1
I followed l
Hi,
I want to continue with the Setup (installation, repair or remove) only if
the following registry key is found.
'Test Folder do not exist'>REGISTRYSEARCH=#1
I followed like this but it doesn't show me the message even if the Test Folder
is not found. If the Test Folder is n
Dyson, Peter wrote:
> What are the issues in getting just the Value from a reg search without
> the prepended #?
>
MSI doesn't support it. Take a look at the MSI SDK doc for the
RegLocator table, which is what RegistrySearch elements turn into:
The installer adds a prefix to the registry valu
I am trying to be nice to users upgrading from one version (or rolling
back) and use the general method of creating a default value which the
user can override in the install, or may override by editing the
registry value itself later on (perfectly valid in the context of the
applications, things c
42 matches
Mail list logo
