Using any x64, AMD64 and Intel64 is not an option due to the legacy code base and linking (The installation has 64 bit files that are not distributed on a 32 bit machine. It also has 64 bit files and 32 bit files that need to go into the same directory due to upgrading on 64 bit machines.)
Note that the same topic also states "If the platform specification is missing in the Template Summary property value, the installer assumes the Intel architecture."? (Intel means 32-bit in this context.)
What you have to watch out for is your target location. Windows Installer itself doesn't care if your file contains 32-bit or 64-bit or even platform-independent data. All it cares about is whether the location you are installing to is a 32-bit or 64-bit location. If you're just installing mixed files under a location that isn't specifically 64-bit, just mark your package as 32-bit (Intel). If you sometimes want to target 64-bit locations, and you want to install on 32-bit machines, you must create multiple packages.
