Exported functions in tests

Zebediah Figura z.figura12 at gmail.com
Fri Oct 13 09:55:26 CDT 2017

On 10/13/2017 02:21 AM, Alexandre Julliard wrote:
> Zebediah Figura <z.figura12 at 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?

More information about the wine-devel mailing list