As quoted by Bob Arnson"You can do everything (and more) that XmlFile supports with XmlConfig but it requires extra authoring that's not necessary with XmlFile. XmlFile is best at modifying XML files that you're installing (e.g., to add an attribute reflecting the installed path of a file); it can't remove the modifications at uninstall time but if your setup installed the file, it will be uninstalled anyway. XmlConfig is best at modifying shared XML files because it supports uninstalling the modifications."
To run a custom action for a specific feature you need include the feature action state value in the condition logic.For example:<Custom Action="MyAction" After="InstallFiles">(NOT Installed) AND (&MyFeature=3)</Custom>The & in front of the feature name will return the feature's action state. Possible action states are: So to only run a custom action for a particular feature we check that it's action state is set to INSTALLSTATE_LOCAL which is 3.Links:MSDN - Conditional Statement SyntaxMSDN - Examples of Conditional Statement SyntaxNabble WiX Forum Item
Taken from Wikipedia entry List of XML and HTML character entity references :
The following SQL will return all English error codes and messages:
WHERE msglangid = 1033
ORDER BY Error
It returns about 7549 rows:
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.