Thanks for the advice. I've looked into client extensions and all the
samples I found seem to work like a charm (for now). In my oppinoin, they
are even easier to implement (from a C++ perspective). I don't know why I
always thought Exchange client extensions only 'extend' the Exchange MAPI
provider (whatever that is - MSEMS probably). I suppose the name is a bit
misleading. So I've scraped my initial ideas of writing a COM add-in.
> In Outlook 2002 you can use Namespace.MAPIOBJECT which evaluates to
> IMAPISession. In Outlook 2000 calling MAPILogonEx() (and praying that you
> are picking up the right session) is the only thing you can do.
> IMsgStore objects are not directly accessible from OOM.
> Since you are using C++, why not write an Exchange Client Extension?
> Dmitry Streblechenko (MVP)
> OutlookSpy - Outlook, CDO
> and MAPI Developer Tool
> > Hi!
> > I have just begun developing an Outlook add-in in C++. As it turns out,
> > OOM itself is somewhat limited in comparison to MAPI.
> > I know it is possible to obtain MAPI interfaces from OOM objects.
> > Specifically I am looking for IMAPISession and IMsgStore (for each
> > the current profile). Could anyone point me in the right direction
> > (preferably some sample code - in C++ would be best, but VB would do as
> > well).
> > Thanks in advance, Andrej