How to target 32bit and 64bit a .NET applications with WiX and separate MSI packages

Target 32bit and 64bit .NET applications

This post will explain how you can build msi packages using WiX for both 32bit and 64bit platforms.  The goal is to create 2 different msi packages. One for 64bit systems, which will install the program in to c:\Program Files on 64bit, and another msi package that will install the program in to c:\Program Files on 32 bit systems. The .NET application itself will be compiled with CPU target Any, which results in that it will run in 64bit mode on 64bit systems and 32bit mode on 32bit systems. Of course, you could also install the 32bit msi package on 64bit systems, which will end up being installed in c:\Program Files (x86).


Microsoft Visual Studio 2008

In my environment, I used 64bit Windows7, so I installed the 64bit version of WiX build 3.0.5419.0-x64-setup

Create a simple .NET application

We will create a simple .NET Winforms application that will show some platform information, like this:



We will also create a WiX setup project and configure a new platform type in Visual Studio for the 64bit target.

Fire up Visual Studio and create a new Windows Forms project:


Add 3 labels to the form:


Add code in the Form Load event to fill the labels with info:



Create a Wix project

Add a new project to the solution, a WiX Setup project:


In the Product.wxs file, enter the following code:


And add references to WixUIExtension.dll and WixUtilExtension.dll.

What you will notice now is that you have 3 targets in your configuration:


The value you choose here will be transferred to the Platform variable in WiX. Unfortunately, the 64bit option is missing, so we must create that one.

Create a x64 configuration entry

Select the Configuration Manager.


Select  <New…>



Select the x64 option and click Ok.


When you now build the Wix project, the output will be created in a new x64 folder. In the Product.wxs code, we also have a title that indicates that is runs in 64bit mode:



When installed, it will end up in c:\Program Files, just as we wanted.

The 32bit version of the msi is built when you select the x86 platform target




Hope this shed some light on how to deploy .NET applications for multiple targets.

Download the complete solution here.

DEBUG: Error 2769: Custom Action install did not close 1 MSIHANDLEs.

You may have seen this strange error when trying to install your MSI when you have developed a managed custom action DLL in Visual Studio 2005 / 2008?

If you execute the MSI with detailed logging, like this:
MSIEXEC /i "<YOURMSI>.msi" /L*v "InstallLog.txt"

You end up with an error message that is similar to this in the log file:
DEBUG: Error 2769:  Custom Action _E3EBB591_EA21_438E_AEB9_4442A5A8C483.install did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: _E3EBB591_EA21_438E_AEB9_4442A5A8C483.install, 1,
Action ended 16:09:12: InstallExecute. Return value 3.

The thing is that you probably have set the Custom Action Data as follows:
The solution to the problem is to add a trailing backslash:

This is actually described in this MSDN article:

How to debug Custom Actions in a MSI setup package

So you have come to the conclusion that you will need to debug custom actions in a MSI setup package?. How do you do it? Well, it’s very simple, just add the following line in your custom action code:


And now when you launch the MSI package, it will break and prompt you with the following dialog:

Choose debugger

Just select the desired debugging environment and start debugging. It’s as simple as that!