After a little further investigation, let me rephrase my initial question and supporting details:
I'm building an MSI using WiX3, and I'm encountering a problem: I've a custom action: <CustomAction Id="EXEREG_PckgInstllr" FileKey="PckgInstllr.exe" ExeCommand="/REGSERVER" Return="ignore" Execute="commit" Impersonate="no" /> It is sequenced to be executed BEFORE 'InstallFinalize'. I've confirmed this using Orca. The problem I encounter is that once the installer is complete the log indicates no error, but the installed application throws a 'class not registered' error. The registry contains no trace of the registered EXE either. If, however I execute 'PckgInstllr.exe /regserver' from a DOS prompt, then the installed app works, and the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\PckgInstllr.EXE\AppID is set to its GUID. Setting Execute to 'defer' or 'commit' makes no difference. The new clue is that if I set Return to 'check' then MSIEXEC detects a failure and rolls back. But executing the same registration call from a DOS prompt does not fail. I've even tried removing the calls and placing them in a BAT file and installing that instead and running it. Again, the log shows it as done but the installed app does not see the registered class. I'm sure I'm missing something so stupid and minor that I'll slap my forehead about it, but right now I haven't a clue. Thanks for any isight you can provide. Raj ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users