On 18/01/2010 08:46, Alexandre Julliard wrote:
This seemed to be the easiest and most trivial way to allow
MAPIInitialize to succeed in the tests, which will be added in the
next several patches.
That doesn't seem right. The tests should be able to work without an
extended provider.
Indeed,
Andrew Nguyen arethus...@gmail.com writes:
This seemed to be the easiest and most trivial way to allow
MAPIInitialize to succeed in the tests, which will be added in the
next several patches.
That doesn't seem right. The tests should be able to work without an
extended provider.
--
On Mon, Jan 18, 2010 at 8:46 AM, Alexandre Julliard julli...@winehq.org wrote:
Andrew Nguyen arethus...@gmail.com writes:
This seemed to be the easiest and most trivial way to allow
MAPIInitialize to succeed in the tests, which will be added in the
next several patches.
That doesn't seem
Andrew Nguyen arethus...@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:
