I think you’d have to write your own VB script/DLL custom action to:
1. Read the user’s input from a property
2. Read the existing value from the registry -
http://stackoverflow.com/questions/34065/how-to-read-a-value-from-the-windows-registry
3. Write a property (or don’t) if the user’s
I think you’d have to write your own VB script/DLL custom action to:
1. Read the user’s input from a property
2. Read the existing value from the registry -
http://stackoverflow.com/questions/34065/how-to-read-a-value-from-the-windows-registry
3. Write a property (or don’t) if the user’s input
I have been searching around for a while without luck on the approach
used to initiate a RegistrySearch using a value entered in a text field
when the user presses next in a dialog.
The best I could come up with was publishing a DoAction
Trying that again...
I have been searching around for a while without luck on the approach
used to initiate a RegistrySearch using a value entered in a text field
when the user presses next in a dialog.
The best I could come up with was publishing a DoAction event in the
next button control.
Well, it's a little bit embarrasing, but i've already found what was the
issue. There was a typo in the registry path.
Anyway, thank's for your effort.
Mateusz
--
View this message in context:
Hi,
I'm trying to determine what if a version of PostgreSQL is installed on a
windows 8.1 64 bit machine, using the following code:
*util:RegistrySearch Root=HKLM Id=PostgreSearch Win64=yes
Key=SOFTWARE\PostgreSQL\Installations\posgresql-x64-9.3 Value=Version
Variable=PostgreVersion /*
But when
Are you having the same problem as the Poster here:
http://stackoverflow.com/questions/19227335/wix-burn-3-7-and-postgresql-registry-search-fail
Did the answer help?
Carter
Quoting vorsichtdiekurve mp.mateusz.polan...@gmail.com:
Hi,
I'm trying to determine what if a version of PostgreSQL is
Unfortunately, it didn't.
My problem is that the registry key is not being found, not that the
registry search is not being executed.
Here is my bootsrapper code:
Bundle Name=Setup Version=1.0.0.0 Manufacturer=Company
UpgradeCode=3731eedd-c21c-40e2-bf03-653ea4a186e2
On 7/23/2014 8:51 PM, vorsichtdiekurve wrote:
Unfortunately, it didn't.
My problem is that the registry key is not being found, not that the
registry search is not being executed.
Here is my bootsrapper code:
Bundle Name=Setup Version=1.0.0.0 Manufacturer=Company
Is this a 64/32bit registry type issue?
And is the burn package being run with elevated privileges? (just to rule
out issues with registry permissions)
Regards,
Bevan
Date: Wed, 23 Jul 2014 00:38:22 -0700 (PDT)
From: vorsichtdiekurve mp.mateusz.polan...@gmail.com
Subject: [WiX-users
.MSSQLSERVER\Setup]
on the value SQLPath or SqlProgramDir.
Regards,
Mike
-Original Message-
From: Brett Faurot [mailto:Brett.Faurot@]
Sent: Tuesday, June 10, 2014 12:51 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] RegistrySearch doesn't find Key
Thank you
. It's frustrating when such a simple thing
causes a dead stop in work.
-Original Message-
From: Phil Wilson [mailto:phildgwil...@gmail.com]
Sent: Saturday, June 07, 2014 1:56 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] RegistrySearch doesn't find Key
Hi Brett,
Can you post the code of how you are using this property in your code?
--Pavan
-Original Message-
From: Brett Faurot [mailto:brett.fau...@dh.com]
Sent: Tuesday, June 10, 2014 12:51 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] RegistrySearch
-
From: Brett Faurot [mailto:brett.fau...@dh.com]
Sent: Friday, June 06, 2014 12:32 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch doesn't find Key
I'm having problems using a registrysearch. I'm trying to get the install
location of MS SQL Reporting Services
[mailto:brett.fau...@dh.com]
Sent: Friday, June 06, 2014 12:32 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch doesn't find Key
I'm having problems using a registrysearch. I'm trying to get the install
location of MS SQL Reporting Services by checking the registry
I'm having problems using a registrysearch. I'm trying to get the install
location of MS SQL Reporting Services by checking the registry; but, my
installer is failing the find the key.
Property Id=REPORTINGSERVICESPROP
RegistrySearch Id=SqlSearch Root=HKLM
I'm having problems using a registrysearch. I'm trying to get the install
location of MS SQL Reporting Services by checking the registry; but, my
installer is failing the find the key.
Property Id=REPORTINGSERVICESPROP
RegistrySearch Id=SqlSearch Root=HKLM
Try putting type =directory
-Original Message-
From: Brett Faurot [mailto:brett.fau...@dh.com]
Sent: Friday, June 06, 2014 12:32 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch doesn't find Key
I'm having problems using a registrysearch. I'm trying to get
, not the
Package/@Platform attribute.
That is a doc bug. Please file it so we get it corrected.
-Blair
Date: Wed, 27 Nov 2013 19:46:10 +0200
From: igor@gmail.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch/@Win64 bug?
Hello,
RegistrySearch/@Win64
@gmail.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch/@Win64 bug?
Hello,
RegistrySearch/@Win64 documentation at
http://wixtoolset.org/documentation/manual/v3/xsd/wix/registrysearch.html
says:
The default value depends on the value of the Package/@Platform
Hello,
RegistrySearch/@Win64 documentation at
http://wixtoolset.org/documentation/manual/v3/xsd/wix/registrysearch.html
says:
The default value depends on the value of the Package/@Platform attribute:
if the @Platform attribute value is 'x86', the default @Win64 attribute
value is 'no';
: Wednesday, 28 August 2013 3:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch example in tutorial
The original registry search you posted doesn't have Win64=yes so it will be
a 32-bit registry search if you have an x86 platform install (and it looks
create using
the WiX toolset.
From: rob...@softdev.net
To: wix-users@lists.sourceforge.net
Date: Wed, 28 Aug 2013 07:33:17 +
Subject: Re: [WiX-users] RegistrySearch example in tutorial
Hi Phil/Blair,
I'm just trying to get through the tutorial on a x64 machine. The problem was
resolved
: Mon, 26 Aug 2013 23:52:18 +
Subject: Re: [WiX-users] RegistrySearch example in tutorial
Thanks for both replies. I am indeed on a x64 machine and have no idea how to
distinguish between x86/x64 registries. I've probably created the key in the
wrong one. Any pointers? To open the editor, I
: [WiX-users] RegistrySearch example in tutorial
Thanks for both replies. I am indeed on a x64 machine and have no idea
how to distinguish between x86/x64 registries. I've probably created the
key in the wrong one. Any pointers? To open the editor, I type in regedit
If not that, then how
I'm a novice user, going through Getting Started. I cannot get the
RegistrySearch to work, or FILEEXISTS - both from Where to Install? page in
your tutorial.
I suspect it is because this element:
Property Id=INSTALLDIR
RegistrySearch Id='AcmeFoobarRegistry' Type='raw' Root='HKLM'
Date: Mon, 26 Aug 2013 06:31:51 +
Subject: [WiX-users] RegistrySearch example in tutorial
I'm a novice user, going through Getting Started. I cannot get the
RegistrySearch to work, or FILEEXISTS - both from Where to Install? page in
your tutorial.
I suspect it is because this element
Do you have a 32-bit MSI and are trying to read a 64-bit registry
location, per chance? Or vice versa?
From: rob...@softdev.net
To: wix-users@lists.sourceforge.net
Date: Mon, 26 Aug 2013 06:31:51 +
Subject: [WiX-users] RegistrySearch example in tutorial
I'm a novice user, going
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch example in tutorial
What often happens is that there is a custom action to set the default
INSTALLDIR location to the program files folder, and people forget to make it
conditional, with a condition
Hi all,
I ran into the strangest problem on a customer's machine today. He was
installing a new version (MAJOR upgrade) of our software which has the
authoring below. We set INSTALLDIR from UPGRADEDIR if a previous
version is installed (SetUpgradeInstallDir custom action) and make the
Can anyone tell me if I have done anything wrong here, it does not seem to
be working. And also do I have to call a custom action to run this search?
Whats my best way for testing it?
Property Id=PRODUCTINSTALLED
RegistrySearch Id=PRODUCTINSTALLED Root=HKLM
-users] RegistrySearch
Can anyone tell me if I have done anything wrong here, it does not seem to be
working. And also do I have to call a custom action to run this search?
Whats my best way for testing it?
Property Id=PRODUCTINSTALLED
RegistrySearch Id=PRODUCTINSTALLED Root=HKLM
Key
: 16 August 2012 14:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch
That looks ok but you don't normally reference WOW6432Node as that
redirection happens automatically if your msi is 32bit.
Neil
-Original Message-
From: Natalie Carr
All,
I have what appears to be a simple chained install using burn, where I would
like to do a RegistrySearch to read a key created by the first msi, and use
that to install the second msi to a subfolder of that location. The first
S3DInstallation.msi has its’ own GUI which is run and
On 01-May-12 16:34, Brian C wrote:
I have what appears to be a simple chained install using burn, where I
would like to do a RegistrySearch to read a key created by the first msi, and
use that to install the second msi to a subfolder of that location.
Burn doesn't support that today. All
Hi,
I am using Windows 7, 64 bit.
I ma having trouble reading if a key exists in registry. The key that I am
using for is in HKLM\Software\Wow6432Node\MyApplication\MyApp.
I am using the following code:
Property Id=ISPRESENT
RegistrySearch Id=PathSearch
Root=HKLM
Type=raw
...@gmail.com]
Verzonden: 30 January 2012 13:34
Aan: wix-users@lists.sourceforge.net
Onderwerp: [WiX-users] RegistrySearch
Hi,
I am using Windows 7, 64 bit.
I ma having trouble reading if a key exists in registry. The key that I am
using for is in HKLM\Software\Wow6432Node\MyApplication\MyApp.
I am
Subject: [WiX-users] RegistrySearch
Hi,
I am using Windows 7, 64 bit.
I ma having trouble reading if a key exists in registry. The key that I am
using for is in HKLM\Software\Wow6432Node\MyApplication\MyApp.
I am using the following code:
Property Id=ISPRESENT
RegistrySearch Id=PathSearch
van Peppen
Senior System Engineer
Insad Grafisch b.v.
-Oorspronkelijk bericht-
Van: loyalty Reddy [mailto:reddy.loya...@gmail.com]
Verzonden: 30 January 2012 13:34
Aan: wix-users@lists.sourceforge.net
Onderwerp: [WiX-users] RegistrySearch
Hi,
I am using Windows 7, 64 bit.
I ma
in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP
Email Disclaimer
-Original Message-
From: loyalty Reddy [mailto:reddy.loya...@gmail.com]
Sent: 30 January 2012 12:37
To: wix-users@lists.sourceforge.net
Subject: [WiX-users
Reddy [mailto:reddy.loya...@gmail.com]
Verzonden: 30 January 2012 15:51
Aan: General discussion for Windows Installer XML toolset.
Onderwerp: Re: [WiX-users] RegistrySearch
And how can I check if ISPRESENT is empty or not?
On Mon, Jan 30, 2012 at 2:16 PM, Albert van Peppen alb...@insad.nl wrote
toolset.
Subject: Re: [WiX-users] RegistrySearch
I did remove Wow6432Node and also Win64 element. I just want to know at the
end if ISPRESENT is empty ot not. HOw do I check that? If ISPRESENT is
empty, I want to enable a control.
On Mon, Jan 30, 2012 at 2:29 PM, Pally Sandher pally.sand
Message-
From: loyalty Reddy [mailto:reddy.loya...@gmail.com]
Sent: 30 January 2012 14:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch
I did remove Wow6432Node and also Win64 element. I just want to know at the
end if ISPRESENT is empty ot
Hello all,
I am having some problems with an installation using Wix v3
During install of application I run
Property Id=SETUPFOLDER
RegistrySearch Id=SETUPFOLDER Root=HKCU
Key=SOFTWARE\$(var.Company)\$(var.Product)\Common Name=SetupFolder
Type=raw /
/Property
SETUPFOLDER is later used for
What does the verbose log file show?
On Tue, Oct 25, 2011 at 8:10 AM, Leo Koivuniemi
universalserial...@gmail.com wrote:
Hello all,
I am having some problems with an installation using Wix v3
During install of application I run
Property Id=SETUPFOLDER
RegistrySearch Id=SETUPFOLDER
Hi,
thanks for fast reply!
In the MSI log I can see that it actually finds the correct SETUPFOLDER path
from registry, but then there are some rows saying:
Ignoring disallowed property SETUPFOLDER
But I can see that it finds the correct path because further down in the log
I have something like
Hi again,
I believe I solved it (haven't done enough testing yet though!)!
It seems that the property had to be set as Secure=yes since otherwise UAC
will not allow it.
Will get back to you if I find that it is not solved. But I just tried an
installation that earlier did not work and now it
Hi,
I'm trying to set a property based on the registry key search. The registry key
as seen in reg editor is
HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\VC\VCRedist\x64
I tried 2 combinations -
1. Set win64=no and specify path without explicit Wow6432Node.
Property
2011 8:24 a.m.
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch under Wow6432Node
Hi,
I'm trying to set a property based on the registry key search. The
registry key as seen in reg editor is
HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\VC\VCRedist\x64
I tried 2
Sadly, the Windows Installer doesn't support that.
On Fri, Nov 19, 2010 at 2:16 PM, Brian Pang bria...@yahoo.com wrote:
Hi,
RegistrySearch for REG_DWORD handling using WiX Installer.
After the RegistrySearch it returns REG_SZ with #1.
How do you resolve this issue so it will set the return
Message-
From: Brian Pang [mailto:bria...@yahoo.com]
Sent: 19 November 2010 22:16
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch for REG_DWORD handling using WiX
Installer
Hi,
RegistrySearch for REG_DWORD handling using WiX Installer.
After the RegistrySearch
{
session[SqlTcpPort] = string.Empty;
}
}
return ActionResult.Success;
}
Neil
-Original Message-
From: Brian Pang [mailto:bria...@yahoo.com]
Sent: 19 November 2010 22:16
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch
Hi,
RegistrySearch for REG_DWORD handling using WiX Installer.
After the RegistrySearch it returns REG_SZ with #1.
How do you resolve this issue so it will set the return type to an REG_DWORD
and
value of 1?
Thanks in advance!
Property Id=PORT Value=12345 RegistrySearch
You could set the property's initial value to something like MY_DUMMY_VALUE and
then check to see if
the property is still equal to it after the registry searching.
Rob
On 26/09/2010 18:39, Sean Farrow wrote:
Hi:
I need to use the RegistrySearch element in a property. I need to look a key
Hi:
I need to use the RegistrySearch element in a property. I need to look a key
who's default key has no default value (regedit show value not set). What
will the property be set to? I'll need to use this property in a launch
condition. Should I do this or could I use a custom action to set
On 26-Sep-10 13:39, Sean Farrow wrote:
I need to use the RegistrySearch element in a property. I need to look a key
who's default key has no default value (regedit show value not set). What
will the property be set to?
Nothing. See the RegLocator doc.
--
sig://boB
http://joyofsetup.com/
of Application Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: Friday, May 14, 2010 7:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch converts
Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: 18 May 2010 15:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch converts value data
%PROGRAMFILES% maps to C
%? It always maps to C:\Program
Files.
Date: Sun, 16 May 2010 19:07:32 +0200
From: eriksson.jim...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] RegistrySearch converts value data
Can you explain the StringTools solution?
2010/5/14 Matt Johnson ma
the environment before printing this e-mail
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: Tuesday, May 18, 2010 8:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch converts value data
ok, now I know
What are you doing with HELPINSTALLERDIR? How are you consuming it?
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: Sunday, May 16, 2010 3:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch converts
-
From: Blair [mailto:os...@live.com]
Sent: Monday, May 17, 2010 3:08 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] RegistrySearch converts value data
What are you doing with HELPINSTALLERDIR? How are you consuming it?
-Original Message-
From
@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch converts value data
Hi
Anyone who can tell me why my RegistrySearch converts the value
contained in the registry?
Property Id=HELPINSTALLDIR
RegistrySearch Id='HelpInstallRegistry' Type='raw' Root='HKLM'
Key
Development
Time America, Inc.
ma...@timeamerica.com | www.timeamerica.com
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: Friday, May 14, 2010 7:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch converts value data
Hi
Anyone
What happens if you specify %PROGRAMFILES%? It always maps to C:\Program Files.
Date: Sun, 16 May 2010 19:07:32 +0200
From: eriksson.jim...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] RegistrySearch converts value data
Can you explain the StringTools solution
-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: Friday, May 14, 2010 7:42 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch converts value data
Hi
Anyone who can tell me why my RegistrySearch converts the value contained in
the registry?
Property Id
...@gmail.com]
Sent: 14 May 2010 15:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch converts value data
Hi
Anyone who can tell me why my RegistrySearch converts the value
contained in the registry?
Property Id=HELPINSTALLDIR
RegistrySearch Id
Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: 14 May 2010 15:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch converts value data
Do you have a directory named HELPINSTALLDIR?
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: Friday, May 14, 2010 9:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch converts value data
Ok, so
On 4/13/2010 10:38 AM, Rodney Schuler wrote:
RegistrySearch Id=TheirProductName Root=HKLM
Key=Software\TheirCompany\TheirProduct\[THEIRCURVER]\[THEIRCURLANG]
Name=ProductName Type=raw/RegistrySearch
You can't rely on using the results of one AppSearch in another like
that because
On 3/16/2010 6:08 AM, Yu, Brian wrote:
How do I check if a registry directory exists or not using
registrysearch?
AppSearch doesn't have that functionality.
--
sig://boB
http://joyofsetup.com/
--
Download
PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] RegistrySearch Type raw causes a '1' to be
writtenin RegLocater table - should be a '2'
Which build of the WiX toolset?
-Original Message-
From: mtoews [mailto:margaret.to...@wolterskluwer.com]
Sent
, January 28, 2010 7:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch Type raw causes a '1' to be
writtenin RegLocater table - should be a '2'
Wix version 2.0.1605.0
Margaret Toews
Programmer Analyst
ProSystem fx Engagement
CCH, a Wolters Kluwer
Wow, that's incredibly ancient - an early development build from 2004 or
earlier. The bits have probably rotted. The release version of WIX 2.0
is 2.0.5805.0 which was released in 2008; since WiX 3.0 was released in
July 2009 though, even that is obsolescent.
If you want to stick to WiX 2.0
Absolutely. Upgrading resolved the issue. Thank you.
--
View this message in context:
http://n2.nabble.com/RegistrySearch-Type-raw-causes-a-1-to-be-written-in-RegLocater-table-should-be-a-2-tp4468104p4476425.html
Sent from the wix-users mailing list archive at Nabble.com.
From a Wix newby: When I use the registrysearch element as below
Property Id='TESTPROPERTYTOSET'
RegistrySearch Id='NewSignature1'
Type='raw'
Root='HKLM'
Which build of the WiX toolset?
-Original Message-
From: mtoews [mailto:margaret.to...@wolterskluwer.com]
Sent: Wednesday, January 27, 2010 8:14 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] RegistrySearch Type raw causes a '1' to be written in
RegLocater table - should
G
reat, thanks.
--
Thanks,
Kevin Garman, Project Engineer
SCADAware, Inc.
www.scadaware.com
On Tue, 2009-12-22 at 10:12 +1100, Sascha Beaumont wrote:
The documentation indicates that it happens during AppSearch
(http://msdn.microsoft.com/en-us/library/aa367578(VS.85).aspx) -
Hi,
Can anyone tell me when the RegistrySearches are evaluated in terms of
InstallUISequence and InstallExecuteSequence actions? For some reason I
was thinking it happens during AppSearch but now I can find evidence of
that.
Thanks,
Kevin
The documentation indicates that it happens during AppSearch
(http://msdn.microsoft.com/en-us/library/aa367578(VS.85).aspx) -
RegistrySearch elements map to the RegLocator table in the MSI.
The AppSearch action searches for signatures using the CompLocator table
first, the RegLocator table
Hello all,
I encountered the following strange issue.
I have a property defined like that:
Property Id=DLL_INSTALLED
RegistrySearch Id=Dll Root=HKCR Key=Dll.Dll Type=raw /
/Property
The problem is that the RegistrySearch behaves differently when running with
UI and without it.
When I
And how about QWORD value?
-Original Message-
From: Alex Shevchuk [mailto:shevc...@live.com]
Sent: Tuesday, May 12, 2009 01:04
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] RegistrySearch and RegistryValue
Hi Alex,
Short answer: Yes, maybe
, May 11, 2009 10:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] RegistrySearch and RegistryValue
Is it possible to use RegistrySearch result in RegistryValue? Something
like this:
Property Id=PROP1
RegistrySearch Id=search1
Root=HKLM
Is it possible to use RegistrySearch result in RegistryValue? Something
like this:
Property Id=PROP1
RegistrySearch Id=search1
Root=HKLM
Key=somekey
Name=somename
Type=raw /
/Property
...
RegistryValue Type=???
Hi,
I have a product that is installed using MSI created using Wix. The product
can host different Plugins that are also installed using WIX MSI packages.
The main application is writing the INSTALLDIR to the registry so the
installers for the Plugins know where they should be installed. This
I have the following registry searches, the 1st one fails on _some_ machines,
the 2nd works as expected.
Property Id=MY_EXISTING_TARGETDIR Secure=yes
RegistrySearch Id=TargetDirSearch Root=HKLM
Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch: remove #
In article [EMAIL PROTECTED],
Neil Sleightholm [EMAIL PROTECTED] writes:
Actually it is much simpler than that, I want to read the SQL port
number from the registry and then open it in the firewall but to do
the
write
In article [EMAIL PROTECTED],
Neil Sleightholm [EMAIL PROTECTED] writes:
Actually it is much simpler than that, I want to read the SQL port
number from the registry and then open it in the firewall but to do the
write I need the number without the hash.
Then you'll need to write a CA to
It there anyway to remove the hash (#) from the start of a
RegistrySearch if the value is a DWORD?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
-
This SF.Net email is sponsored by the Moblin Your Move
In article [EMAIL PROTECTED],
Neil Sleightholm [EMAIL PROTECTED] writes:
It there anyway to remove the hash (#) from the start of a
RegistrySearch if the value is a DWORD?
I'm guessing the reason you want this is so that you can do numeric
comparisons on a DWORD value in a condition?
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch: remove #
In article [EMAIL PROTECTED],
Neil Sleightholm [EMAIL PROTECTED] writes:
It there anyway to remove the hash (#) from the start of a
RegistrySearch if the value is a DWORD?
I'm guessing
Hi, I have several custom dialogs in my installer allowing the user to
enter SQL Server connection details and active directory settings.
I don't want the user to have to re-enter this information each time
they install a new version/reinstall, so I have made it so that during
the install, each
I tried that but for some reason it just allways shows the hard coded
value and not the registry value.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 30 October 2008 16:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
@lists.sourceforge.net
Sent: Thursday, August 21, 2008 1:37 AM
Subject: [WiX-users] RegistrySearch question
I am trying to read a Registry setting to get the installed instances of
SQL
Server. The InstalledInstances entry is a REG_MULTI_SZ data type. There is
a
value entered in this entry but the property
] On Behalf Of Mike Rerick
Sent: Wednesday, August 20, 2008 4:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] RegistrySearch question
I am trying to read a Registry setting to get the installed instances of SQL
Server. The InstalledInstances entry is a REG_MULTI_SZ data
Rerick
Sent: Wednesday, August 20, 2008 4:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] RegistrySearch question
I am trying to read a Registry setting to get the installed instances of SQL
Server. The InstalledInstances entry is a REG_MULTI_SZ data type
I'm trying to get the default SQL Server Instance using the following:
Property Id=SQL_INS RegistrySearch Id=SQL_INS_SRC
Root=HKLMKey=SOFTWARE\Microsoft\Microsoft SQL Server
Name=InstalledInstances Type=raw//Property
This SHOULD return one or more values in the format
Looks like retrieving a reg_multi_sz using the RegLocator table during
AppSearch is not a great way of doing this. Plenty of places on the web
document this oddity. I think you might just want to use a custom action
instead of a registry search to retrieve this value and write it to a
property.
Sent: Thursday, July 31, 2008 11:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch on a REG_MULTI_SZ
Looks like retrieving a reg_multi_sz using the RegLocator table during
AppSearch is not a great way of doing this. Plenty of places on the web
or is there some other sort of
CA that I can use?
Thank you for responding
-Original Message-
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of Dana Gutride
Sent: Thursday, July 31, 2008 11:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
1 - 100 of 112 matches
Mail list logo
