Hi There,
According to the AppDeploy.com Package KB:
http://www.appdeploy.com/software/detail.asp?id=153476This is already 2 MSI based installations wrapped up into a single setup.exe file.
So, unfortunately, this is as good as it gets for 32/64 bit deployment, since you can't wrap up both installers into a single MSI package. And the logic to determine which one gets installed has to come in the form of a controlling process that makes the call which MSI package to run (in this case, setup.exe).
What's the use case you have for this? It might be possible to extract the *.msi packages from the executable and work with them that way.