FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

MAPI and .Net

SGriffin's MAPI Internals — Fri, 03 Apr 2009 18:27:11 GMT

Working with a customer the other day, I went looking for my blog post discussing the fact that MAPI

Unsupported Messaging API’s in Managed code – Outlook Add-ins

Le Café Central de DeVa — Thu, 19 Feb 2009 04:36:03 GMT

Certain technologies that predate the .NET Framework are not supported in managed code programming. These

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

Petri — Fri, 30 Nov 2007 23:27:44 GMT

I thought WebDAV is available only on local server, so remotely it is not available. Maybe I was wrong.

And yes, I saw the E2007 SP1 web services, and what that offer :-)

And yes, I meant folder's ACLs in Mailbox.

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

Matt Stehle - MSFT — Fri, 30 Nov 2007 15:34:43 GMT

I just realized that above you mentioned mailbox permissions not folder permissions. If you are setting permissions at the mailbox level in Exchange 2000/2003 then you can use CDOEXM or modify the AD objects using ADSI, etc.

In Exchange 2007 you can use the Add-ADPermission and Add-MailboxPermission cmdlets.

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

Matt Stehle - MSFT — Fri, 30 Nov 2007 15:25:47 GMT

You can edit the ACLs of folders using WebDAV in Exchange 2000/2003 - fully supported from .NET...

http://msdn2.microsoft.com/en-us/library/aa123902.aspx

You can use Exchange Web Services in Exchange 2007 SP1...

http://msdn2.microsoft.com/en-us/library/bb856574.aspx

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

Petri X — Fri, 30 Nov 2007 09:53:21 GMT

Oh ! Wonderful but too painful article ! Even it might be truth.

Some of us knows how limited Exchange is for the mailbox permissions, so I'm looking for the solution like this (including change the ACLs on the folders):

http://support.microsoft.com/kb/240911

But on this blog you say that, nobody should follow above article anymore, unless use C++/VB6.

Could you point me out which of these:

http://support.microsoft.com/kb/813349

support ACL modifications on the mailbox level ?

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

Matt Stehle - MSFT — Fri, 30 Nov 2007 01:17:41 GMT

If you are running a desktop application then you can use OOM rather than CDO 1.21 to get to the GAL. In Outlook 2003 OOM doesn't have the PropertyAccessor which gives you greater access to properties on an item so many developers want to use CDO 1.21. This isn't an impossibility you just need to do it out of process from your managed code...

http://blogs.msdn.com/mstehle/archive/2007/07/27/howto-delete-search-folders-and-interop-with-cdo-1-21-from-managed-net-code.aspx

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

joycek — Fri, 30 Nov 2007 01:04:48 GMT

So if you need a replacement for CDO 1.21 from a client APP that is not a web app to an Exchange server that could be 200/3/7 or unknown What Then?

You can't access the address book or the GAL from a desktop app with webDav - no? (in OL2003) OL2007 has some CDO function built in but not OL2003...

If CDO 1.21 is available but not .NET supported that means it is implicit that apps must be dev in unmanaged languages like C++ ?

Sending mail is not really the problem it's accessing other object on Exchange servers.

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

Matt Stehle - MSFT — Sat, 24 Nov 2007 00:51:08 GMT

This doesn't change anything about Outlook Object Model - as I said above it is fully supported in managed code.

I'm not sure where VSTO fits into this discussion because it is just an AddIn model for Outlook. If you can expand on that question, I"ll take a crack at it...

re: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

Brian — Thu, 22 Nov 2007 17:29:40 GMT

So where does this leave Visual Studio Tools for Office? Particularly the ability to write managed code against the Outlook object model? Presumably the VSTO libraries are COM based under the wrappers, but they will still run in-process?