Hi folks,

I am developing an outlook com addin. Because the outlook object model
is limited it resorts to extended mapi in many fields. Reading about
the latest exchange developments there is stated that Mapi32 is
deemphasized. Does that also mean that extended mapi won't work in
future versions of outlook, meaning my com addin will be useless?

Cheers,
Ron.

Hi Roice,

I am developing an outlook com addin. Because the outlook object model
is limited it resorts to extended mapi in many fields. Reading about
the latest exchange developments there is stated that Mapi32 is
deemphasized. Does that also mean that extended mapi won't work in
future versions of outlook, meaning my com addin will be useless?

Where did you read about deemphasized ExMAPI?

--
SvenC

Hello SvenC,

Where did you read about deemphasized ExMAPI?

sorry, I did not read this, therefore the subject line is not correct
and was meant as a question.

With the introduction of exchange 2007 there are a lot of
functionalities which are called deemphasized, Mapi32 included. That's
why I wanted to know if the usage of extended mapi inside a com addin
would be affected too. Sorry if that's a silly question, but my
knowledge about outlook/exchange technologies is really limited.

Ron.

Hi Roice,

Where did you read about deemphasized ExMAPI?

sorry, I did not read this, therefore the subject line is not correct
and was meant as a question.

With the introduction of exchange 2007 there are a lot of
functionalities which are called deemphasized, Mapi32 included.

Again: where do read or hear about mapi32 deemphasized?

There is nothing mentioned from Microsoft:
http://technet.microsoft.com/en-us/l.../aa998911.aspx

So I expect MAPI to be around for quite a while. It was
actually the *only* API which lasted since Exchange 5 (don't
know what earlier version used, could have been MAPI as
well).

All the other APIs come and go (cdoex, edoexm, exoledb,
WebDAV, ISF you name them).

--
SvenC

There is nothing mentioned from Microsoft:http://technet.microsoft.com/en-us/l.../aa998911.aspx

That's exactly the document that I meant: There is stated the
following:

Deemphasized Functionality

There are legacy Exchange features that are now being deemphasized in
Exchange 2007:
Public folders - Free/busy calendaring functionality is provided by
the Availability service. If you need additional functionality,
migrate to SharePoint Portal Server or a similar product.
Proxy address generators - Use the Exchange Management Shell.
CDO 1.2.1 - This functionality is provided by the Exchange Web
Services.
MAPI32 - This functionality is provided by the Exchange Web Services.
CDOEX (CDO 3.0) - This functionality is provided by the Exchange Web
Services.
Exchange WebDAV extensions - This functionality is provided by the
Exchange Web Services.
ExOLEDB - This functionality is provided by the Exchange Web Services.
Store events - This functionality is provided by the Notification Web
service.
Streaming backup APIs.
Exchange 2003 Virus Scanning Application Programming Interface (VSAPI).

Hi Roice,

There is nothing mentioned from
Microsoft:http://technet.microsoft.com/en-us/l.../aa998911.aspx

That's exactly the document that I meant: There is stated the
following:

Deemphasized Functionality
CDO 1.2.1 - This functionality is provided by the Exchange Web
Services.
MAPI32 - This functionality is provided by the Exchange Web Services.

Sorry - I stopped reading at this one:
MAPI client and CDO 1.2.1 on the Exchange installation
Exchange 2007 no longer depends on these components. They are a separate
component that will be available for download. For more information about
how to download the required components, see Microsoft Exchange Server MAPI
Client and Collaboration Data Objects 1.2.1

So you do not get MAPI installed on the Exchange Server itself. But you can
happily install the ExchangeMAPICDO package or even Outlook to get MAPI on
the server. But more important to me is that MAPI access to the server is
working and there is no statement that MAPI client access id deemphasized.
At least as long as Outlook Clients are supported there should be MAPI
access guaranteed.

You might get an answer from Microsoft (mainly Stephen Griffin) when you ask
this question in ms.public.win32.programmer.messaging

--
SvenC

Outlook is entirely MAPI based, it would have to be rewritten from scratch
to not use MAPI. Same for Exchange server. ECE's aren't going to be
supported for Outlook in the future, but you still will be able to write COM
addins using Extended MAPI.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Roice" wrote in message
...

Hi folks,

I am developing an outlook com addin. Because the outlook object model
is limited it resorts to extended mapi in many fields. Reading about
the latest exchange developments there is stated that Mapi32 is
deemphasized. Does that also mean that extended mapi won't work in
future versions of outlook, meaning my com addin will be useless?

Cheers,
Ron.