The custom action is called from the MSI, right? So if it's unmanaged
(not DTF) it will be an msiexec.exe process. Windows will launch or
use an appropriate bitness msiexec.exe process to call the CA. The
bootstrapper is a diferent process, so I don't see how there could be
a connection. An immedia
I have two custom action functions (A and B) that use LoadLibraryEx() to
load a DLL that already exists on the target system (NOT installed by my
MSI) and then proceeds to call a few functions in that DLL. My MSI is
installed by the WiX Standard Bootstrapper. These custom actions functions
in a tot
2 matches
Mail list logo