Windows Installer
 
Unrestricted access to Windows Installer functionality!
 
Open Source
 
Open source!
 

<xml/>

 
Plain XML based source scripts!
 
Free
 
Free, no strings attached!
 
Build Automation
 
Command-line interface for automated application build process!
 
Community
 
Thriving community support!
Why WiX?
ICE11

What does ICE11 check?

ICE11 validates that a nested MSI installation custom action has a valid identifier for the source. Technically, ICE11 checks the Source column of the CustomAction table for Nested Installation custom actions. The Source column must contain a valid GUID (MSI product code).

Note: The valid format for a GUID is {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} where X is a hex digit (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F). Utilities such as GUIDGEN can generate GUIDs containing lowercase letters. These must all be changed to uppercase letters before the GUID can be used by the installer as a valid product code, package code, or component code

When does ICE11 show up?

ICE11 posts an error if the Source column of the CustomAction table is authored incorrectly for nested installation custom actions.

How can I fix ICE11?

The source of a Nested Installation custom action must contain a valid GUID. So, you should update the source value so that it can represent a valid MSI product code.