My bad, I always forget that. For binaries, the Windows Installer peeks at the executable binary and figures out how to host it. "Any CPU" managed code assemblies a 'architecture preference' (default is x86, IIRC). You can change that preference at build time, IIRC.
_____________________________________________________________ Short replies here. Complete answers over there: http://www.firegiant.com/ -----Original Message----- From: wixtester [mailto:sangee...@hotmail.com] Sent: Wednesday, January 7, 2015 6:49 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] CustomAction 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 ---------------- error CNDL0037: The CustomAction/@Win64 attribute can only be specified with one of the following attributes:Script, VBScriptCall, or JScriptCall present. Note: I am using managed custom action because of some additional processing required, after the JRE version is identified. Thanks much! ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
