Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
Also if these are shared COM components (installed by other products) it's probably not a good idea to give the user a choice at install time. You want them in a common location (but separated by bitness). Phil Wilson -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: Thursday, March 11, 2010 5:33 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder? On 3/11/2010 6:02 PM, Paul Baker wrote: We give the user a choice of install location for our 64-bit components, which defaults to Program Files\Product Name. Should we create a parallel Program Files (x86)\Product Name folder for the 32-bit components? If so, what should happen if the user decides to install the 64-bit components to a different location? Personally, I'd vote for nothing. Unless a product is bigger than, say, 100MB, even folks like me who partition their drives tightly to keep small C: drives won't much care. (Remember that MSI keeps a copy of your .msi and Windows 7, it's the whole .msi.) One alternative that I have seen several times is to install the 32-bit components into Program Files (x86)\Common Files. Are there any drawbacks to going against the stated purpose of CommonFilesFolder (for components that are shared across applications) in this way? Not that I know of. The most important thing is to keep files in the right directory tree according to bitness. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
just put 32-bit components in the 32-bit file system. Fortunately in this case that is an option. Are there any recommendations on exactly where these components should go? We give the user a choice of install location for our 64-bit components, which defaults to Program Files\Product Name. Should we create a parallel Program Files (x86)\Product Name folder for the 32-bit components? If so, what should happen if the user decides to install the 64-bit components to a different location? One alternative that I have seen several times is to install the 32-bit components into Program Files (x86)\Common Files. Are there any drawbacks to going against the stated purpose of CommonFilesFolder (for components that are shared across applications) in this way? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
On 3/11/2010 6:02 PM, Paul Baker wrote: We give the user a choice of install location for our 64-bit components, which defaults to Program Files\Product Name. Should we create a parallel Program Files (x86)\Product Name folder for the 32-bit components? If so, what should happen if the user decides to install the 64-bit components to a different location? Personally, I'd vote for nothing. Unless a product is bigger than, say, 100MB, even folks like me who partition their drives tightly to keep small C: drives won't much care. (Remember that MSI keeps a copy of your .msi and Windows 7, it's the whole .msi.) One alternative that I have seen several times is to install the 32-bit components into Program Files (x86)\Common Files. Are there any drawbacks to going against the stated purpose of CommonFilesFolder (for components that are shared across applications) in this way? Not that I know of. The most important thing is to keep files in the right directory tree according to bitness. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
On 3/6/2010 8:22 PM, Paul Baker wrote: We're now thinking of registering our COM server using RegistryValue elements, where RegistryValue/@Key contains Wow6432Node. Does anyone know of any potential problems with this approach? You might want to listen to what the code is telling you: What you're doing isn't supported; just put 32-bit components in the 32-bit file system. -- sig://boB http://joyofsetup.com/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
On 08/03/2010 13:37, Bob Arnson wrote: On 3/6/2010 8:22 PM, Paul Baker wrote: We're now thinking of registering our COM server using RegistryValue elements, where RegistryValue/@Key contains Wow6432Node. Does anyone know of any potential problems with this approach? You might want to listen to what the code is telling you: What you're doing isn't supported; just put 32-bit components in the 32-bit file system. We ran into a similar set of issues and went for the simple approach of putting the 32 bit components under Directory/@Id=CommonFilesFolder. It has the disadvantage that we're forcing the files onto the system disk, rather than giving the user the choice of where to install them, but in our case they were small enough for this not to be a big issue. -- Cheers, John -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
This should work as long as your installation is running on a x64 Windows. Best regards, Sebastian Brand http://blog.sebastianbrand.com -Original Message- From: Paul Baker [mailto:paulbak...@gmail.com] Sent: Sunday, March 07, 2010 02:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder? Is there a recommended way to install [COM registration] information into the 32-bit part of the registry from a 64-bit (Win64=yes) component? We're now thinking of registering our COM server using RegistryValue elements, where RegistryValue/@Key contains Wow6432Node. Does anyone know of any potential problems with this approach? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
Is there a recommended way to install [COM registration] information into the 32-bit part of the registry from a 64-bit (Win64=yes) component? We're now thinking of registering our COM server using RegistryValue elements, where RegistryValue/@Key contains Wow6432Node. Does anyone know of any potential problems with this approach? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
We're currently building an MSI targeting the x64 platform. Most of our binaries are 64-bit, so we have placed each one into a 64-bit component under the ProgramFiles64Folder directory. However, we also need to install a 32-bit COM in-process server DLL. We're having issues because we'd ideally like this to be placed alongside the rest of our binaries - inside ProgramFiles64Folder. I believe the standard way to install an in-process server DLL is to use a single component containing both a File element and a Class element, the latter for the COM registration information. Unfortunately, this doesn't work in our case - for the registration information to be handled correctly the component must be 32-bit (Win64=no). However, if is then it placed under ProgramFiles64Folder, Light generates an error: ICE80: 32BitComponent uses 64BitDirectory. Is there any way we can get this to work? Approaches we have considered include: 1. Placing the File element and the Class element into different components, so that one can be 64-bit and the other 32-bit. This seems to work but causes Light to generate a warning: ICE69: Mismatched component reference. Is this something to be worried about? 2. Using some alternative method to install the COM registration information. Is there a recommended way to install such information into the 32-bit part of the registry from a 64-bit (Win64=yes) component? 3. Giving up and placing the COM DLL alone inside ProgramFilesFolder. Are there any other ways to get what we'd like: all of our files in the same location? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder?
My advice would be to use the 32 bit install location, but if you really want to put it in the 64 bit location, you can author two components, one for the server and one for the class associated with the server. The server can be marked as 64 bit. The class component marked as x86. Mark the Class element as Advertise=no, which makes the registration use the registry table instead of the class table. In this context you can reference the server by its file ID using the Server=fileId attribute on the class element. However, depending on how complex your class definition is, there are bugs in WIX that can make defining the class with advertise=no painful. Also, this arrangement may give a different warning about the file reference being outside of the component that defines it, but that they are both part of the same feature. This warning is ignorable in the given scenario, but I don't know if that is sufficient for you. -- Bryan -Original Message- From: Paul Baker [mailto:paulbak...@gmail.com] Sent: Wednesday, March 03, 2010 1:40 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Is it possible to install a 32-bit COM server DLL under ProgramFiles64Folder? We're currently building an MSI targeting the x64 platform. Most of our binaries are 64-bit, so we have placed each one into a 64-bit component under the ProgramFiles64Folder directory. However, we also need to install a 32-bit COM in-process server DLL. We're having issues because we'd ideally like this to be placed alongside the rest of our binaries - inside ProgramFiles64Folder. I believe the standard way to install an in-process server DLL is to use a single component containing both a File element and a Class element, the latter for the COM registration information. Unfortunately, this doesn't work in our case - for the registration information to be handled correctly the component must be 32-bit (Win64=no). However, if is then it placed under ProgramFiles64Folder, Light generates an error: ICE80: 32BitComponent uses 64BitDirectory. Is there any way we can get this to work? Approaches we have considered include: 1. Placing the File element and the Class element into different components, so that one can be 64-bit and the other 32-bit. This seems to work but causes Light to generate a warning: ICE69: Mismatched component reference. Is this something to be worried about? 2. Using some alternative method to install the COM registration information. Is there a recommended way to install such information into the 32-bit part of the registry from a 64-bit (Win64=yes) component? 3. Giving up and placing the COM DLL alone inside ProgramFilesFolder. Are there any other ways to get what we'd like: all of our files in the same location? -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
