Zebediah Figura z.figura12@gmail.com writes:
On 10/13/2017 02:21 AM, Alexandre Julliard wrote:
Zebediah Figura z.figura12@gmail.com writes:
Does anyone know, or have a hunch, as to what the problem might be here? For what it's worth, it's known that native MSI uses a separate process to execute custom actions, although I don't know how this would lend any clue to what's going wrong.
In a separate process you'd already have the MSI server exe running, so you can't load a second exe. What probably happens is that the exe module is loaded but its imports are not resolved.
Why does this happen for the test module but not for existing custom action DLLs?
DLLs can be loaded in the server process, but an exe can't.