enry.com
www.jackhenry.com
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Friday, March 21, 2014 12:26 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] util:RegistrySearch “Registry key not found” when
using variable inside Win64=“$(var.Win64)”
I also stopp
I also stopped using Win64, but you need to make sure that the -arch flag is
being passed on the command line to candle and light. One way to do this is
to add the InstallerPlatform MSBuild Property to your project file. You can
unload your project file, and edit it, adding the following statemen
Interesting, I was able to get it to work by simply removing the Win64
attribute altogether. I swear I tried this before and it didn't work...
Just needed a nights sleep I guess.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/util-RegistrySearch-
I do not use the Result attribute, but other than that I do use
Win64=$(var.Win64) for two util:RegistrySearch elements. One returns an
Install Location, and one returns and integer. Both work fine.
The installer/bootstrapper is re-compiled each time depending on whether it is
x64 or x86.
--
It's ok, I found a work around here:
http://sourceforge.net/mailarchive/message.php?msg_id=30030043
On Sat, Dec 15, 2012 at 2:33 PM, up2date.cyb...@gmail.com <
up2date.cyb...@gmail.com> wrote:
> Hi, in a bundle, using util:RegistrySearch, is there a way to set a
> default value to a variable?
> W
ists" Variable="TestSearch" />
> Variable="Test" Condition="TestSearch" />
>
> Is this a bug?
>
> Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 30 October 2012 13:55
> To: G
October 2012 13:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] util:RegistrySearch default value
Does it work if you define the Variable and give it a value? The RegistrySearch
runs later and should update it.
On Mon, Oct 29, 2012 at 3:05 PM, Neil Sleightho
Does it work if you define the Variable and give it a value? The
RegistrySearch runs later and should update it.
On Mon, Oct 29, 2012 at 3:05 PM, Neil Sleightholm wrote:
> Is it possible to set a variable to a default value if a registry value
> doesn't exist when using the util:RegistrySearch i
There is a dream that it'd work in both but that dream has not been
realized yet.
On Fri, Oct 26, 2012 at 10:19 AM, Nick Ramirez wrote:
> Seems to be Burn specific and sets a Burn variable while the other
> RegistrySearch that's not in the UtilExtension sets a Property.
>
>
>
> --
> View this mes
Seems to be Burn specific and sets a Burn variable while the other
RegistrySearch that's not in the UtilExtension sets a Property.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/util-RegistrySearch-tp7581620p7581624.html
Sent from the wix-users m
There is one very good reason to use it in an MSI, you can read dword values
without the # on it.
-Original Message-
From: Georg von Kries [mailto:g...@creativbox.net]
Sent: 26 October 2012 17:33
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re:
Hi Neil!
There is no need for the Util extension in an MSI for a registry search.
Just use the normal RegistrySearch element (from the Wix schema) which
populates MSIs RegLocator table. Because of this I think it is burn
specific.
Regards,
Georg von Kries
-Ursprüngliche Nachricht-
Von:
You should be able to use it in both...
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: October-26-12 12:18 PM
To: General toolset. (wix-users@lists.sourceforge.net)
Subject: [WiX-users] util:RegistrySearch
Can the util:RegistrySearch be used in an MSI or is i
The RegistrySearch in the Util extension is only supported in Bundles today.
On Sat, Nov 27, 2010 at 3:21 AM, Sean Farrow
wrote:
> Hi:
> Is it possible to have the util:RegistrySearch elements evaluated before
> the AppSearch custom action.
> I've got conditions in the appsearch that only need to
14 matches
Mail list logo
