Discussion:
[WiX-users] Util RegistrySearch Element and Win64 attribute
ptr
2013-04-05 12:09:01 UTC
Permalink
Util RegistrySearch has an attribute Winb64 that seems to be no by default.
If this is set to Yes, Would it mean it would look in the 32bit registry
on 32bit OS and 64bit registry on 64bit OS ?

The reason I am seeking some clarification is become some other attributes
like these seem to be have different default values for x64 vs x86
configurations.

If you have a boostrapper project that has both x64 and x86 configurations,
Does it have any effect on the final exe. I mean on attribute default
values somewhere ?


Thanks
Raj
Rob Mensching
2013-04-05 12:53:05 UTC
Permalink
The Win64 attribute defaults to 'yes' or 'no' based on the value you pass
to the candle.exe -arch switch. If Win64 is 'no' it searches 32-bit. If it
is 'yes' it will search 64-bit on 64-bit machine and 32-bit on a 32-bit
machine (because there is no 64-bit).

Bootstrapper is completely separate and is not affected by the MSI build.
Post by ptr
Util RegistrySearch has an attribute Winb64 that seems to be no by default.
If this is set to Yes, Would it mean it would look in the 32bit registry
on 32bit OS and 64bit registry on 64bit OS ?
The reason I am seeking some clarification is become some other attributes
like these seem to be have different default values for x64 vs x86
configurations.
If you have a boostrapper project that has both x64 and x86 configurations,
Does it have any effect on the final exe. I mean on attribute default
values somewhere ?
Thanks
Raj
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
ptr
2013-04-05 13:59:52 UTC
Permalink
Thanks Rob.. I just wanted to clarify it because the documentation seems
out of date.

*RegistrySearch documentation says*

Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry. 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'; otherwise, the default value is 'yes'.

*Util Extension RegistrySearch documentation says*
Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry. The
default value is 'no'.

So it seems like even though the bootstrapper is always 32bit it matters
what its build configuration. We have installers that only allow 32bit on
32bit OS and 64bit components on 64bit OS. I am making a boostrapper that
has 32bit components as well as 64bit components as downloaded msis that
have installcondition based on bitness of the OS. I was wondering if
setting winb64 to yes is the right thing. It seems like it is.

Thanks
Raj
Post by Rob Mensching
The Win64 attribute defaults to 'yes' or 'no' based on the value you pass
to the candle.exe -arch switch. If Win64 is 'no' it searches 32-bit. If it
is 'yes' it will search 64-bit on 64-bit machine and 32-bit on a 32-bit
machine (because there is no 64-bit).
Bootstrapper is completely separate and is not affected by the MSI build.
Post by ptr
Util RegistrySearch has an attribute Winb64 that seems to be no by
default.
Post by ptr
If this is set to Yes, Would it mean it would look in the 32bit registry
on 32bit OS and 64bit registry on 64bit OS ?
The reason I am seeking some clarification is become some other
attributes
Post by ptr
like these seem to be have different default values for x64 vs x86
configurations.
If you have a boostrapper project that has both x64 and x86
configurations,
Post by ptr
Does it have any effect on the final exe. I mean on attribute default
values somewhere ?
Thanks
Raj
------------------------------------------------------------------------------
Post by ptr
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Rob Mensching
2013-04-05 14:28:10 UTC
Permalink
Sorry, my bad. I didn't realize you were talking about the
util:RegistrySearch. My answer was about the MSI based RegistrySearch.
Using util:RegistrySearch is explicit. If you say Win64='yes' then the
search is 64-bit and vice versa. You can ignore the fact that the Burn
engine is 32-bit. It matters none.
Post by ptr
Thanks Rob.. I just wanted to clarify it because the documentation seems
out of date.
*RegistrySearch documentation says*
Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry. The
is 'no'; otherwise, the default value is 'yes'.
*Util Extension RegistrySearch documentation says*
Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry. The
default value is 'no'.
So it seems like even though the bootstrapper is always 32bit it matters
what its build configuration. We have installers that only allow 32bit on
32bit OS and 64bit components on 64bit OS. I am making a boostrapper that
has 32bit components as well as 64bit components as downloaded msis that
have installcondition based on bitness of the OS. I was wondering if
setting winb64 to yes is the right thing. It seems like it is.
Thanks
Raj
Post by Rob Mensching
The Win64 attribute defaults to 'yes' or 'no' based on the value you pass
to the candle.exe -arch switch. If Win64 is 'no' it searches 32-bit. If
it
Post by Rob Mensching
is 'yes' it will search 64-bit on 64-bit machine and 32-bit on a 32-bit
machine (because there is no 64-bit).
Bootstrapper is completely separate and is not affected by the MSI build.
Post by ptr
Util RegistrySearch has an attribute Winb64 that seems to be no by
default.
Post by ptr
If this is set to Yes, Would it mean it would look in the 32bit
registry
Post by Rob Mensching
Post by ptr
on 32bit OS and 64bit registry on 64bit OS ?
The reason I am seeking some clarification is become some other
attributes
Post by ptr
like these seem to be have different default values for x64 vs x86
configurations.
If you have a boostrapper project that has both x64 and x86
configurations,
Post by ptr
Does it have any effect on the final exe. I mean on attribute default
values somewhere ?
Thanks
Raj
------------------------------------------------------------------------------
Post by Rob Mensching
Post by ptr
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Post by Rob Mensching
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
ptr
2013-04-05 14:40:29 UTC
Permalink
But what you said about

if I set Win64='yes'
It will do 64bit search on 64bit OS
and on 32bit OS it will do 32bit search and not fail.

is still true for Util:RegistrySearch like it is for MSI RegistrySearch

I suppose I could test this out myself but I just wanted to know if this is
documented behavior and not likely to break in future.

-Raj
Post by Rob Mensching
Sorry, my bad. I didn't realize you were talking about the
util:RegistrySearch. My answer was about the MSI based RegistrySearch.
Using util:RegistrySearch is explicit. If you say Win64='yes' then the
search is 64-bit and vice versa. You can ignore the fact that the Burn
engine is 32-bit. It matters none.
Post by ptr
Thanks Rob.. I just wanted to clarify it because the documentation seems
out of date.
*RegistrySearch documentation says*
Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry.
The
value
Post by ptr
is 'no'; otherwise, the default value is 'yes'.
*Util Extension RegistrySearch documentation says*
Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry.
The
Post by ptr
default value is 'no'.
So it seems like even though the bootstrapper is always 32bit it matters
what its build configuration. We have installers that only allow 32bit on
32bit OS and 64bit components on 64bit OS. I am making a boostrapper that
has 32bit components as well as 64bit components as downloaded msis that
have installcondition based on bitness of the OS. I was wondering if
setting winb64 to yes is the right thing. It seems like it is.
Thanks
Raj
Post by Rob Mensching
The Win64 attribute defaults to 'yes' or 'no' based on the value you
pass
Post by ptr
Post by Rob Mensching
to the candle.exe -arch switch. If Win64 is 'no' it searches 32-bit. If
it
Post by Rob Mensching
is 'yes' it will search 64-bit on 64-bit machine and 32-bit on a 32-bit
machine (because there is no 64-bit).
Bootstrapper is completely separate and is not affected by the MSI
build.
Post by ptr
Post by Rob Mensching
Post by ptr
Util RegistrySearch has an attribute Winb64 that seems to be no by
default.
Post by ptr
If this is set to Yes, Would it mean it would look in the 32bit
registry
Post by Rob Mensching
Post by ptr
on 32bit OS and 64bit registry on 64bit OS ?
The reason I am seeking some clarification is become some other
attributes
Post by ptr
like these seem to be have different default values for x64 vs x86
configurations.
If you have a boostrapper project that has both x64 and x86
configurations,
Post by ptr
Does it have any effect on the final exe. I mean on attribute default
values somewhere ?
Thanks
Raj
------------------------------------------------------------------------------
Post by ptr
Post by Rob Mensching
Post by ptr
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Post by ptr
Post by Rob Mensching
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Post by ptr
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Rob Mensching
2013-04-05 14:55:01 UTC
Permalink
I think that's reasonable. If you could test it out and file a bug saying,
"This is what I discovered, it would be ideal if the documentation defined
the expected behavior for util:RegistrySearch Win64." I'll get the right
thing to happen on the other side. <smile/>
Post by ptr
But what you said about
if I set Win64='yes'
It will do 64bit search on 64bit OS
and on 32bit OS it will do 32bit search and not fail.
is still true for Util:RegistrySearch like it is for MSI RegistrySearch
I suppose I could test this out myself but I just wanted to know if this is
documented behavior and not likely to break in future.
-Raj
Post by Rob Mensching
Sorry, my bad. I didn't realize you were talking about the
util:RegistrySearch. My answer was about the MSI based RegistrySearch.
Using util:RegistrySearch is explicit. If you say Win64='yes' then the
search is 64-bit and vice versa. You can ignore the fact that the Burn
engine is 32-bit. It matters none.
Post by ptr
Thanks Rob.. I just wanted to clarify it because the documentation
seems
Post by Rob Mensching
Post by ptr
out of date.
*RegistrySearch documentation says*
Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry.
The
if
Post by Rob Mensching
value
Post by ptr
is 'no'; otherwise, the default value is 'yes'.
*Util Extension RegistrySearch documentation says*
Instructs the search to look in the 64-bit registry when the value is
'yes'. When the value is 'no', the search looks in the 32-bit registry.
The
Post by ptr
default value is 'no'.
So it seems like even though the bootstrapper is always 32bit it
matters
Post by Rob Mensching
Post by ptr
what its build configuration. We have installers that only allow 32bit
on
Post by Rob Mensching
Post by ptr
32bit OS and 64bit components on 64bit OS. I am making a boostrapper
that
Post by Rob Mensching
Post by ptr
has 32bit components as well as 64bit components as downloaded msis
that
Post by Rob Mensching
Post by ptr
have installcondition based on bitness of the OS. I was wondering if
setting winb64 to yes is the right thing. It seems like it is.
Thanks
Raj
Post by Rob Mensching
The Win64 attribute defaults to 'yes' or 'no' based on the value you
pass
Post by ptr
Post by Rob Mensching
to the candle.exe -arch switch. If Win64 is 'no' it searches 32-bit.
If
Post by Rob Mensching
Post by ptr
it
Post by Rob Mensching
is 'yes' it will search 64-bit on 64-bit machine and 32-bit on a
32-bit
Post by Rob Mensching
Post by ptr
Post by Rob Mensching
machine (because there is no 64-bit).
Bootstrapper is completely separate and is not affected by the MSI
build.
Post by ptr
Post by Rob Mensching
Post by ptr
Util RegistrySearch has an attribute Winb64 that seems to be no by
default.
Post by ptr
If this is set to Yes, Would it mean it would look in the 32bit
registry
Post by Rob Mensching
Post by ptr
on 32bit OS and 64bit registry on 64bit OS ?
The reason I am seeking some clarification is become some other
attributes
Post by ptr
like these seem to be have different default values for x64 vs x86
configurations.
If you have a boostrapper project that has both x64 and x86
configurations,
Post by ptr
Does it have any effect on the final exe. I mean on attribute
default
Post by Rob Mensching
Post by ptr
Post by Rob Mensching
Post by ptr
values somewhere ?
Thanks
Raj
------------------------------------------------------------------------------
Post by Rob Mensching
Post by ptr
Post by Rob Mensching
Post by ptr
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Post by Rob Mensching
Post by ptr
Post by Rob Mensching
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Post by Rob Mensching
Post by ptr
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Post by Rob Mensching
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Phill Hogland
2015-07-22 12:15:24 UTC
Permalink
"Util RegistrySearch has an attribute Winb64 that seems to be no by default.
If this is set to Yes, Would it mean it would look in the 32 bit registry
on 32bit OS and 64bit registry on 64 bit OS ? "

Yes. but the attribute is RegistrySearch/@Win64. In the default situation
where it is no or does not exist, I think the OS "redirects" registry access
based on the bitness of the bundle.exe, which today is always a 32 bit
bundle.exe. (There is dev discussion about creating a 64 bit version of Burn
in a future release.) When RegistrySearch/@Win64='yes' the OS redirection,
which would normally take place, is bypassed and the 64 bit registry is
used. Generally I only provide this attribute when I specifically need to
look for a registry key in the 64 bit area from my Burn bundle.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Util-RegistrySearch-Element-and-Win64-attribute-tp7584914p7600918.html
Sent from the wix-users mailing list archive at Nabble.com.

Loading...