Hi Doug,
I have the Install Parameters/Package type set to Mixed 32/64-bit (based on an earlier search that forced me to do that because of the version of DIFXAPP.DLL that is needed).
Since your package type is a mixed package type, then the package runs as a 32-bit package on 32-bit systems and as a 64-bit package on x64 systems. It allows you to have a single installation package that will install on both platform types (32-bit and 64-bit platforms) and can install files or registry in the real system paths regardless of the platform. The mixed package feature is offered by our EXE bootstrapper. It detects the target platform and automatically configures the internal MSI package.
The EXE file built by Advanced Installer is a 32 bit one, this contains the x86 and x64 MSI files as well as the files to be installed from the CAB. When launched the EXE checks for the OS architecture and it launches the correct MSI.
When a 32-bit application writes or reads a value under the C:\Windows\System32 directory , the application reads from the C:\Windows\SysWOW64 directory on a 64-bit OS.
Their 32-bit counterparts are resolved to redirected locations as follows:
- ProgramFilesFolder - C:\Program Files (x86)\
- CommonFilesFolder - C:\Program Files (x86)\Common Files\
- SystemFolder - C:\Windows\SysWOW64\
This is the default behavior for Windows Installer. A 32-bit installation package, on 64-bit machines, cannot install resources into 64-bit locations (i.e. "Program Files" folder).
So, first off...Does my application need to be in the x86 folder?
The encountered behaviour is correct. Your application should not be installed in the x86 folder as the package type is a mixed package type.
If so, then how do I get it there without breaking the installation?
Why would you like to install under the x86 folder? Does it not work as expected if it is installed in the x64 bit section of the Program Files (C:\Program Files)?
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging