Re: [WiX-users] Quiet Execution of an executable embedded within the MSI

2010-06-18 Thread Jeremy Farrell
> Sent: Friday, June 18, 2010 4:29 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Quiet Execution of an executable > embedded within the MSI > > Binary Elements are extracted to temporary directories using auto > generated filena

Re: [WiX-users] Quiet Execution of an executable embedded within the MSI

2010-06-18 Thread Leigh Wetmore
Thanks for the responses - I've gone with the file element. I don't really want the executable written to disk (it serves no purpose to the end user), but there's no harm in it being there. On Fri, Jun 18, 2010 at 7:28 AM, Pally Sandher wrote: > Binary Elements are extracted to temporary directo

Re: [WiX-users] Quiet Execution of an executable embedded within the MSI

2010-06-18 Thread Pally Sandher
Binary Elements are extracted to temporary directories using auto generated filenames (see a verbose log for an example). It's not possible to use an application in a Binary Element with QtExec (I looked at the same thing a while ago for a plug-in installer). You'll either need to change it to use

Re: [WiX-users] Quiet Execution of an executable embedded within the MSI

2010-06-17 Thread Blair
Things in the Binary table are only extracted when other code calls the APIs to extract them, so the/a custom action would be required to know to get it from there. To make it more complicated, the extraction code must be run from an immediate action, so an immediate/deferred pair (immediate to "st