Could WiX be launching the CA as in 32-bit mode? -----Original Message----- From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com] Sent: Thursday, July 01, 2010 1:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows 7 Custom Action Registry problem
yeah, I thought about that. it is a C# custom action built for the "Any CPU" platform running on a 64-bit OS in a 64-bit WiX install. I don't know how it could possibly be 32-bit. -----Original Message----- From: Simon Dahlbacka [mailto:simon.dahlba...@gmail.com] Sent: Thursday, July 01, 2010 1:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows 7 Custom Action Registry problem that seems to indicate that your custom action is running as 32-bit, if you run them as 64-bit things should just work.. On Thu, Jul 1, 2010 at 10:09 PM, Kurt Jensen <kurt.jen...@ophir-spiricon.com> wrote: > That's it! > > So far I cannot find an equivalent in .NET but at least now I can track down > the communication breakdown... > > Thanks to all! > > > -----Original Message----- > From: i...@roadrunner.com [mailto:i...@roadrunner.com] > Sent: Thursday, July 01, 2010 11:23 AM > To: General discussion for Windows Installer XML toolset. > Cc: Kurt Jensen > Subject: Re: [WiX-users] Windows 7 Custom Action Registry problem > >> also, this solution was developed by another less install oriented >> programmer for the original vsproj under VS2008. I moved the code >> as-is over to WiX on a 32-bit install and it worked. now we are >> adding a 64-bit install. if I change to having Windows Installer do >> the job then I really am reinventing the wheel from our perspective. > > Maybe your keys get redirected? Check > HKLM\SOFTWARE\Wow6432Node\Spiricon\Version5. Maybe your values are there. > If so, you need to add KEY_WOW64_64KEY to RegOpenKey (or whatever the .NET > equivalent is). > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > > www.clearswift.com > ********************************************************************** > > > ---------------------------------------------------------------------- > -------- This SF.net email is sponsored by Sprint What will you do > first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
