InstallExecuteSequence is always called. However when running with full UI it goes InstallUISequence first followed by InstallExecuteSequence which is why your code is working now. When running with basic (/qb) or no (/qn) UI it only runs the InstallExecuteSequence.
What I was trying to highlight was that you were looking at the wrong place in your log file. The InstallUISequence shows up as "MSI (c)" in the log where as the InstallExecuteSequence shows up as "MSI (s)" (c = client, s = server). I wasn't recommending you change it to the InstallUISequence as it's not going to work now if your users run your installer without any UI (test it for yourself & see). If you're happy with that behaviour then fair enough but I've seen enough corporate & even end-user installation scenarios where full UI isn't used to know that you should never rely on it. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Lukas Haase [mailto:lukasha...@gmx.at] Sent: 23 July 2010 13:18 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] InstallExecuteSequence completely ignored 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 ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
