Building 32-bit DLL's etc on 64-bit Server
Are there any implications of building 32-bit dll's (C++/C#) on Windows 2008 R2 (64-bit
Also what are peoples thoughts on repackaging 32-bit software on a Windows 7 32-bit image for deployment to Windows 2008R2 ?
Answers (2)
The trick with packaging 32-bit software on W7 32-bit for deployment on W2K8R2 that you may run into is where the system puts the files. On 64-bit systems, the 32-bit files and registry keys go into different places because they have the 64-bit locations as the default install points. You may or may not find this causes problems when transferring.
I do not know about building dlls on 64 bit. The trick with packaging 32-bit software on W7 32-bit for deployment on W2K8R2 that you may run into is where the system puts the files. On 64-bit systems, the 32-bit files and registry keys go into different places because they have the 64-bit locations as the default install points. For instance, on W2K8R2, the default Program Files folder is the 64-bit folder, and 32-bit software goes in Program Files (x86). On W2KR2 the default ODBC control panel is the 64-bit ODBC. You may or may not find this causes problems when transferring.
This post might help you to create packages for x64
http://msiworld.blogspot.com.au/2011/09/creating-msi-for-x64-and-x86-machines.html
