Wix Interactions with Conditions, Properties & Custom Actions

http://www.mail-archive.com/[email protected]/msg05097.html gives an solution to republish the properties that were changed in the custom action immediately after it. Here is an example of how I have gotten it to work in my code: <?xml version=”1.0″ encoding=”utf-8″?> <Wix xmlns=”http://schemas.microsoft.com/wix/2006/wi”> <Fragment> <Binary Id=”ConnectionStringExtension.dll” SourceFile=”$(var.ConnectionStringExtension.TargetDir)$(var.ConnectionStringExtension.TargetName).CA.dll” /> <CustomAction Id=”MyCustomAction” BinaryKey=”ConnectionStringExtension.dll” DllEntry=”VerifyConnectionString” Execute=”immediate” /> <UI> <Dialog Id=”ConnectionStringDlg” Width=”370″ Height=”270″ Title=”Database … Read more

Forcing an upgrade of a file that is modified during its initial installation

Newer answers: 1) Companion files, 2) file version hack using Visual Studio, 3) moving the file to another installation path, 4) variations of REINSTALLMODE, 5) “version lying”, etc… All kind of options, most of which are not ideal: File of a new component isn’t installed because there was an old component with the same file … Read more

Wix Tools update uses old custom actions

Testing the Conditions Condition #1: Installed AND (NOT REMOVE=”ALL” OR UPGRADINGPRODUCTCODE) This rather odd constellation of conditioning will cause the custom action in question to not run during a fresh install, nor a manual uninstall. It seems this custom action will run during: major upgrade (which is a special type of uninstall), modify and repair. … Read more

wix installer ice03 Invalid Language Id

ICE rules are Internal Consistency Evaluators – essentially a series of self-diagnosis scripts checking database referential integrity, database consistency, data type and schema compliance as well as running several content validation tests or logical tests on the whole MSI (which is really an MS-SQL database in disguise). DB Integrity: In other words you check the … Read more