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 ?

Answer Summary:
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.
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

3

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.

Answered 04/30/2012 by: philologist
Red Belt

Please log in to comment

Answers

1
Answered 04/30/2012 by: piyushnasa
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share