Hi

We've been developing Outlook components for several years. These include
Exchange client extensions, COM Add-ins and Service Providers, all written
in C++. In line with Microsoft our client extensions have virtually
disappeared, and most code is now in the COM Add-in; but with having to
support Outlook 2007, is now the time to move over to C#?

Looking at Outlook 2007 and all of the new features (in particular Ribbon
Bar and Form Regions) it seems that most (if not all) examples are provided
in C# (or VB.net, which I'm not considering). My experimenting with C# tell
me it is quick and easy, but what happens if I have to dive into MAPI from
my new C# code (as was often the case in earlier version of our COM Addin).

Any thoughts, experiences are much appreaciated.

Alan.

Outlook 2007 is still COM based, but so you should be able to support it in
a C++ COM add-in easily.
See
http://blogs.msdn.com/jensenh/archiv...c-and-atl.aspx
As for Extended MAPI, forget about it: you can of course use a wrapper like
mapi33 or use a third party wrapper like Redemption, but you won't be able
to access MAPI natively.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Alan" wrote in message
...
Hi

We've been developing Outlook components for several years. These include
Exchange client extensions, COM Add-ins and Service Providers, all written
in C++. In line with Microsoft our client extensions have virtually
disappeared, and most code is now in the COM Add-in; but with having to
support Outlook 2007, is now the time to move over to C#?

Looking at Outlook 2007 and all of the new features (in particular Ribbon
Bar and Form Regions) it seems that most (if not all) examples are
provided in C# (or VB.net, which I'm not considering). My experimenting
with C# tell me it is quick and easy, but what happens if I have to dive
into MAPI from my new C# code (as was often the case in earlier version of
our COM Addin).

Any thoughts, experiences are much appreaciated.

Alan.