Re: [WiX-users] 64-bit Questions
I believe this ends up in the MsiAssemblyName table together with some other assembly name attributes. If you get it wrong the usual symptom is that the assembly won't be uninstalled from the GAC. Assuming this is for the MsiAssemblyName table, IMO WiX should be getting this value for you automatically rather than having you specify it. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 12:35 AM To: [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64-bit Questions Do you also know how the ProcessorArchitecture attribute of the file element is actually used during deployment. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 17 October 2007 06:07 To: Stone, Darren (HBOS FS, IT , DDC Infrastructure) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64-bit Questions [EMAIL PROTECTED] wrote: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). However I am not 100% clear on whether this is neccessary for .Net Assemblies as they are effectively only copied to my deployment directory. If a component is marked as 32-bit, MSI won't put it into 64-bit portions of the file system or registry. * I have also seen posts that state that 32-Bit and 64-Bit components should be deployed to different directories (I have 2 assemblies that need to be 32-Bit and several thousand that should run as 64-Bit!). Is this a neccessity or just good practice, and what is the reason for it. That's more of a Windows thing, keeping 32-bit and 64-bit portions of the system separate. -- sig://boB http://joyofsetup.com/ . HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. == - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit Questions
Do you also know how the ProcessorArchitecture attribute of the file element is actually used during deployment. _ From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 17 October 2007 06:07 To: Stone, Darren (HBOS FS, IT , DDC Infrastructure) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64-bit Questions [EMAIL PROTECTED] wrote: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). However I am not 100% clear on whether this is neccessary for .Net Assemblies as they are effectively only copied to my deployment directory. If a component is marked as 32-bit, MSI won't put it into 64-bit portions of the file system or registry. * I have also seen posts that state that 32-Bit and 64-Bit components should be deployed to different directories (I have 2 assemblies that need to be 32-Bit and several thousand that should run as 64-Bit!). Is this a neccessity or just good practice, and what is the reason for it. That's more of a Windows thing, keeping 32-bit and 64-bit portions of the system separate. -- sig://boB http://joyofsetup.com/ . HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. == - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit Questions
[EMAIL PROTECTED] wrote: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). However I am not 100% clear on whether this is neccessary for .Net Assemblies as they are effectively only copied to my deployment directory. If a component is marked as 32-bit, MSI won't put it into 64-bit portions of the file system or registry. * I have also seen posts that state that 32-Bit and 64-Bit components should be deployed to different directories (I have 2 assemblies that need to be 32-Bit and several thousand that should run as 64-Bit!). Is this a neccessity or just good practice, and what is the reason for it. That's more of a Windows thing, keeping 32-bit and 64-bit portions of the system separate. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] 64-bit Questions
I am attempting to package a .Net 2.0 application for deployment to a server running the 64-Bit version of Windows 2003. Having never attempted a 64 Bit deployment before I would appreciate feedback on the following: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). However I am not 100% clear on whether this is neccessary for .Net Assemblies as they are effectively only copied to my deployment directory. * I have also seen posts that state that 32-Bit and 64-Bit components should be deployed to different directories (I have 2 assemblies that need to be 32-Bit and several thousand that should run as 64-Bit!). Is this a neccessity or just good practice, and what is the reason for it. * Does anybody know of any issues in deploying Windows Services to a 64-Bit platform. It is probably worth mentioning that any deployments will be full, i.e. no patching or upgrades. Also I want the app to always run 64-Bit rather than under WOW. I would really appreciate any feedback on this. cheers . -- HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. == - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
