Ah... thank you! Those omissions of mine seem pretty major - I'm glad you took the time to correct them. Alas, I've tried several variations with no luck - perhaps I'm missing something elementary - but I think I'm a lot closer now, due to your e-mail. Thanks again!
-----Original Message----- From: Julie Campbell [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 20, 2007 1:15 PM To: wix-users@lists.sourceforge.net; Jose Sanchez Saldana (Excell Data Corporation) Subject: Re: [WiX-users] Calling embedded binaries with WIX Custom Actions Jose, There are three things that you missed: In your <CustomAction> element, you should specify the Execute attribute and use "check" (run custom action synchronously, wait for return code) for the Return attribute, like so: <CustomAction Id="NotepadPopUp" BinaryKey="Notepad.exe" ExeCommand="c:\old.txt" Execute="oncePerProcess" Return="check" /> The <Custom> action requires inner text, specifying whether or not to execute the custom action. If you always want to execute the action, you can use 1, like so: <Custom Action="NotepadPopUp" After="InstallFiles">1</Custom> However, realize that this will ALSO run upon uninstall. If you don't want this, try one of these: <Custom Action="NotepadPopUp" After="InstallFiles">NOT Installed</Custom> <Custom Action="NotepadPopUp" After="InstallFiles">NOT REMOVE~="ALL"</Custom> The first will run only upon initial install, not when repairing. The second will not run when removing the entire package. Hope this helps! Julie Campbell [EMAIL PROTECTED] ------------------------------ Message: 6 Date: Mon, 19 Nov 2007 13:09:30 -0800 From: "Jose Sanchez Saldana (Excell Data Corporation)" <[EMAIL PROTECTED]> Subject: [WiX-users] Calling embedded binaries with WIX Custom Actions To: "wix-users@lists.sourceforge.net" <wix-users@lists.sourceforge.net> Message-ID: <[EMAIL PROTECTED] soft.com> Content-Type: text/plain; charset="us-ascii" As a simple test, I've input the following code into a .wxs file: <Binary Id="Notepad.exe" SourceFile="c:\WINNT\notepad.exe"/> <CustomAction Id="NotepadPopUp" BinaryKey="Notepad.exe" ExeCommand="c:\old.txt" /> <InstallExecuteSequence> <Custom Action="NotepadPopUp" After="InstallFiles"/> </InstallExecuteSequence> Thus, I'm trying to get notepad to pop up "old.txt", with no apparent results. The examples and documentation I've looked through suggest this is correct, though - is there anything I might have missed? Thanks. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
