[6/10] winemapi: Add MAPIInitialize implementation.

Alexandre Julliard julliard at winehq.org
Mon Jan 18 10:42:15 CST 2010

Andrew Nguyen <arethusa26 at gmail.com> writes:

> Yes, the mapi32 prop and util tests on Wine don't require the extended
> MAPI provider, but on Windows a MAPI provider must exist in order for
> initialization to succeed. Without a provider, NT platforms simply
> skip:
> prop.c:1380: Tests skipped: ScInitMapiUtil is not implemented
> Currently, the unit tests do this with ScInitMapiUtil, but the problem
> with this approach is that on systems with the Outlook extended MAPI
> provider, initialization with ScInitMapiUtil result in some tests
> triggering a crash within the provider. I've tried to deal with this
> by having the tests initialize with MAPIInitialize, and to make the
> tests pass on Wine also I added the MAPIInitialize function to the
> winemapi provider. Is my approach the best way to achieve the task, or
> should I be doing something else?

The real question is what do we need to do to be able to run on Windows
the tests that don't require an extended provider. If MAPIInitialize
does it fine, but in that case it should do it on Wine too.

Alexandre Julliard
julliard at winehq.org

More information about the wine-devel mailing list