[wix-users] How to specify payload for wix C++ custom action ( WIX version 126.96.36.19907)
Jacob.Hoover at greenheck.com
Wed Aug 10 07:56:29 PDT 2016
You're going to want to embed this DLL into your MSI, so that you can support a naked install without a bundle. Once the DLL is embedded into the MSI, you can use a custom action to extract it before invoking the CA that requires this DLL to be present.
If you delay load the DLL, you should be able to extract the DLL from the MSI Binary table, and then LoadLibrary/GetProcAddress to invoke the 3rd party DLL as needed.
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of shashank khadse
Sent: Wednesday, August 10, 2016 5:07 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: [wix-users] How to specify payload for wix C++ custom action ( WIX version 188.8.131.5207)
I am need to use a third party dll for execution of one of my Wix C++ custom action in msi.
I tried using the payload for MsiPackage , but those payloads are getting copied into the cached directory under the
Since the custom action are getting executed directly under the %Temp% directory
* at runtime *
as per the installer log
"Invoking remote custom action. DLL:
C:\Users\Tom\AppData\Local\Temp\MSIE983.tmp, Entrypoint: RegisterData", the installer crashes with an error "A DLL required for this install to complete could not be run."
Does the dependent dlls also need to be copied at runtime under %temp% directory ?
The cached dlls does not seems to be picked up.
Is there any workaround for this ?
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users