I know that on 64-bit Windows, 32-bit applications by default go to C:\Program Files (x86) and 64-bit to C:\Program Files .
But what if you have a more complex installation package that includes, say, one client component (32-bit) and one server component (64-bit) and, possibly, several auxiliary tools (32-bit). What should be the default installation path in this case?
According to some articles, bit mixing is not recommended by Microsoft and some installation frameworks:
I donโt understand why their mixing should be so big, but it doesnโt matter, considering how well the x64 platform runs x86 applications and, especially, with managed code in which the same binary files can work in both modes. In my case, 75% of the accompanying libraries are shared between the client and server and are completely identical, so it makes no sense to separate them.
So, considering this, what is the preferred installation location for this combination of 32 and 64-bit applications? C:\Program Files (x86) or C:\Program Files ? As I can see, a 64-bit location is preferable. I see the Program Files (x86) directory as an old sandbox for old applications that were never intended for 64-bit applications. In the case of a hybrid 32/64-bit application, there is 64-bit awareness, so there should be no obsolete reason to isolate 32-bit files from 64-bit. For me, a path without "(x86)" is also more visually appealing and indicates that this modern application is adapted for a 64-bit operation (if necessary).
Does anyone know of other reasons or against placing a 32/64-bit set of executable files in a 64-bit directory when installing as one application in one installer package?
Martin Rasmusson
source share