Dear Pally, Am 23.07.2010 11:04, schrieb Pally Sandher: > MSI (c) (74:80) [21:07:26:477]: Doing action: ValidateProductID Aktion > 21:07:26: ValidateProductID. > > That's the InstallUISequence not the InstallExecuteSequence.
Indeed! I changed now to InstallUISequence and now it works! But why? The tutorial clearly states that InstallExecuteSequence is *always* called: "InstallExecuteSequence is always consulted by the installer to determine the actions, InstallUISequence is only considered when the installer runs in full or reduced UI mode (yet another functionality to experiment with, try msiexec /qn, /qb and /qr)" And second, this is the sample from the tutorial: <CustomAction Id="CheckingPID" BinaryKey="CheckPID" DllEntry="CheckPID" /> <CustomAction Id="RefusePID" Error="Invalid key. Installation aborted." /> <InstallExecuteSequence> <Custom Action="CheckingPID" After="CostFinalize" /> <Custom Action="RefusePID" After="CheckingPID">PIDACCEPTED = "0" AND NOT Installed</Custom> </InstallExecuteSequence> <Binary Id="CheckPID" SourceFile="CheckPID.dll" /> It uses InstallExecuteSequence as well! > WiX doesn't "ignore InstallExecuteSequence" as the InstallExecuteSequence is just another database table to WiX. WiX is a way for you to make packages for Windows Installer. If your custom action isn't running, it's highly unlikely the blame can be placed on WiX. Sorry if you got me wrong. Of course, I do NOT want to blame WiX :-) I just did not understand the action is not called (it seemed to me that my sequence was ignored)... Regards, Luke ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
