Incompatibility between x86 and x64 in Installation solution

I have installation solution that have installer project (not web installer but simple installer) that ins开发者_JAVA技巧talls NT services, web service and web sites with help of additional two projects of dlls with my own code that performs my installation step. In user actions of installer project I call installer function of one of those projects, and this project calls to installer of second project: installer -> MiddleCaller -> InstallationCore.

All this developing on Windows 7 and work fine when I compile all in 32 bit.

The project must run on Windows 2008. Because of some reasons all must be in x64 bit.

For this purpose, in MiddleCaller and InstallationCore I click right button of mouse on project -> build -> targer x64. For to move installer project to 64 bit in properties of installer (when project is active) I check: Target platform: x64.

When I run installation on x86 I get error:

The installation package is not supported by this processor type"

And this is good, because now I know that my installation compiled in 64 bit, but when I run this on windows 2008 I get:

Error 1001. Exception occured while initializing the instance:  
System.BadImageFormatException: could not load file or Assembly   
'MiddleCaller, v...' or one of its dependencies. An attempt was  
made to load a program with an incorrect format.  

Any one has some idea what I need to do for run fine the installation on x64?

May be I still not moved the installer project to x64 bit, if yes, where I do this?

Thank you for ahead.

Found a quick tip on Microsoft's website that could be useful on troubleshooting setup and deployment projects:

64-bit managed custom actions throw a System.BadImageFormatException exception

If you add a 64-bit managed custom action to a Setup project, the Visual Studio build process embeds a 32-bit version of InstallUtilLib.dll into the MSI as InstallUtil. In turn, the 32-bit .NET Framework is loaded to run the 64-bit managed custom action and causes a BadImageFormatException exception.

For the workaround, replace the 32-bit InstallUtilLib.dll with the 64-bit version.

Open the resulting .msi in Orca from the Windows Installer SDK.

Select the Binary table.

Double click the cell [Binary Data] for the record InstallUtil.

Make sure "Read binary from filename" is selected and click the Browse button.

Browse to %WINDIR%\Microsoft.NET\Framework64\v2.0.50727.

Note The Framework64 directory is only installed on 64-bit platforms and corresponds to the 64-bit processor type. Select InstallUtilLib.dll.

Click the Open button.

Click the OK button.

There are some unclear things in this scenario. I understand that you are having difficulty running a 32-bit installer that calls on 64-bit assemblies. If this is correct, then what you are doing is not allowed. You cannot have 32-bit and 64-bit assemblies in the same process - that is illegal. If the 64-bit assemblies are being referenced by the installer directly, then the installer must also be 64-bit.

As clarification: I believe a 32-bit installer can install a 64-bit application, but it may only do so by copying the 64-bit files and not by actually making calls into the 64-bit files. The only way this is supported is if the 64-bit files are loaded into a different process and you use IPC to call into them, but even this is likely to be a bad solution.

In your case, I would encourage you to convert your installer into a 64-bit installer.

So, eventually, I compiled MiddleCaller and InstallationCore in AnyCpu mode, when all dll and executables that I need to install were compiled in x64 bit. All this I compiled on Windows 2008 x64 bit with x64 bit outer dependencies (like Oracle client).