Thank you all for suggestions! Truly appreciate all the help.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CustomAction-built-for-AnyCPU-does-not-read-64-bit-registry-hive-tp7598754p7598793.html
Sent from the wix-users mailing list archive at
I may have not been clear in my earlier emails, sorry about that.
I have a C# custom action that uses Microsoft.Win32.RegistryKey. I am
building this custom action with AnyCPU. The custom action searches for JRE
on the system and set a value to Session variable. I have 64-bit JRE
installed on
@lists.sourceforge.net
Subject: Re: [WiX-users] CustomAction built for AnyCPU does not read 64-bit
registry hive
I may have not been clear in my earlier emails, sorry about that.
I have a C# custom action that uses Microsoft.Win32.RegistryKey. I am building
this custom action with AnyCPU. The custom action
@lists.sourceforge.net
Subject: Re: [WiX-users] CustomAction built for AnyCPU does not read 64-bit
registry hive
I may have not been clear in my earlier emails, sorry about that.
I have a C# custom action that uses Microsoft.Win32.RegistryKey. I am building
this custom action with AnyCPU
Regarding the comments about using AnyCPU this blog explains one reason why
on a x64 system AnyCPU runs a 32 bit instance of .Net
http://blogs.microsoft.co.il/sasha/2012/04/04/what-anycpu-really-means-as-of-net-45-and-visual-studio-11/
--
View this message in context:
You should be building separate MSIs for both arcitectures:
http://blogs.msdn.com/b/heaths/archive/2008/01/15/different-packages-are-required-for-different-processor-architectures.aspx
so build an x86 Dll for 32-bit systems and an x64 Dll for 64-bit.
In any case, AnyCpu for a Dll actually means
built for AnyCPU does not read 64-bit
registry hive
The CustomAction does not permit Win64 attribute for a managed custom action
CustomAction Id='customActioncheckJavaHomeEnvVar'
BinaryKey='provisionCA' DllEntry='SearchJRE' Execute=immediate
Return=check Win64=yes/
Error message
The CustomAction does not permit Win64 attribute for a managed custom
action
CustomAction Id='customActioncheckJavaHomeEnvVar'
BinaryKey='provisionCA' DllEntry='SearchJRE' Execute=immediate
Return=check Win64=yes/
Error message
error CNDL0037: The CustomAction/@Win64
Defer it?
On Wed, Jan 7, 2015 at 8:49 PM, wixtester sangee...@hotmail.com wrote:
The CustomAction does not permit Win64 attribute for a managed custom
action
CustomAction Id='customActioncheckJavaHomeEnvVar'
BinaryKey='provisionCA' DllEntry='SearchJRE' Execute=immediate
Return=check
Sorry, for the short response. I have done it by setting conditions. x86 vs
x64.Per Rob's blog, check this out
http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/block_install_on_os.html
and (it is also linked) http://msdn.microsoft.com/library/aa370556.aspx
12:55 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] CustomAction built for AnyCPU does not read 64-bit
registry hive
Hi,
I have a managed custom action to read the registry. I want it to read the
64-bit registry on a 64-bit Windows and 32-bit registry on x86 Windows.
When I
Hi,
I have a managed custom action to read the registry. I want it to read
the 64-bit registry on a 64-bit Windows and 32-bit registry on x86 Windows.
When I build the custom action for AnyCPU, I expect it to work.
But when I run the msi (that invokes this custom action) on Win 2008 R2
which
12 matches
Mail list logo
