Tagged Content List
  • Blog Post: FYI: The MAPI docs have moved...

    The MAPI docs have been revamped and moved from Exchange to Outlook 2007 in MSDN.  As Thom points out - they did great work on these updated docs.  Steve also has a post about this along with an overview.  If you are interested in MAPI, go check them out!
  • Blog Post: FYI: MSDN Protocol Docs...

    Steve posted a link to the MSDN protocol documentation.  He talks about them here and here as well.
  • Blog Post: FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

    The issue of using MAPI or (most commonly) CDO 1.21 in managed (.NET) code is one that comes back to us a lot on the Messaging Developer Support team. Both the messaging technologies in question and the .NET framework have been around for many years at this point. As well have the KB articles that state...
  • Blog Post: FYI: MAPI Subsystem and CDO 1.21 download now available

    You can now download the MAPI subsystem and CDO 1.21 from Microsoft and install them separate from Exchange or Outlook. This is a totally standalone download that is comprised from the Exchange 2003 build tree and is fully supported. Here is the download link… Microsoft Exchange Server MAPI Client...
  • Blog Post: FYI: MAPI Editor Is Here! (Formerly known as MFCMAPI)

    My good friend Steve Griffin has been hard at work updating MFCMAPI to now be worthy of a bland PR branding that strips it of all personality in MAPI Editor. Also he has MAPI Editor added to the Exchange source tree as an official product utility. Read more on his blog... Announcing MAPI Editor...
  • Blog Post: HOWTO: Bind to items from CDO/MAPI using WebDAV

    Summary Using PR_URL_COMPNAME to bind to an item in WebDAV from CDO/MAPI involves understanding the encoding rules for the Exchange version where the item is homed. These rules are different and incompatiable between Exchange 2000, Exchange 2000 SP 1, and Exchange 2003. These rules are not documented...
  • Blog Post: MYTH: Outlook and Exchange Can Reside on the Same Machine

    I had a customer email me today saying they resolved their CDO problem by installing SP 2 on their Exchange server and installing Outlook 2003. Big mistake! It's unfortunate and common but so many people put their Exchange implementations at risk by installing Outlook on top of Exchange. One of our Escalation...
Page 1 of 1 (7 items)