CDO, Outlook, Office and other funstuff

Organizations that chose to skip Vista and wait to for Windows 7 face a number of challenges with Microsoft Office. Typically, these organizations stayed with Office 2003 and are now facing a migration to Office 2010. While the migration itself is pretty straightforward, the applications that depend on Office 2003 are more troublesome. Here is a running list concerning these issues that you should pay attention to. The list also details the replacement technologies for Office type applications and components. So, basically, pick your existing technology, sort through the list and determine if you need to upgrade. I’m trying to keep this simple as possible.


Exchange Web Services (EWS)


  • EWS is available on any computer.
  • EWS is enhanced in versions of Exchange later than Microsoft Exchange Server 2007.
  • Migration is not required. But consider updating your proxy classes and specifying a newer Exchange server version by using the RequestServerVersion property on your proxy class.  

Microsoft Office Outlook Object Model (OOM)


  • OOM is available on any computer that has Outlook installed.
  • Migration from OOM is not required. However, EWS does scale better than OOM.
  • OOM will work for all scenarios. 

MAPI


  • MAPI is available on any Windows based computer.
  • MAPI is supported in Exchange 2010. However, the client DLL of MAPI is no longer being actively developed.
  • The existing MAPI implementation can still be used. You should consider replacing MAPI with EWS in Exchange 2010 or the Exchange Web Services Managed API.
  • If an application needs to use MAPI, use the MAPI implementation that ships with Outlook 2007.

 


WebDAV



  • WebDAV is available on any Windows based computer that is using the standard HTTP/HTTPS protocol (Port 80 or 443).
  • WebDAV is deprecated in Exchange 2010.
  • Applications that use Exchange WebDAV should use EWS in Exchange 2010 or the Exchange Web Services Managed API.

 


ExOLEDB


  • ExOLEDB is only available on the Exchange server.
  • This technology is commonly used together with Collaboration Data Objects for Exchange (CDOEX) 3.0.
  • ExOLEDB is deprecated in Exchange 2010.
  • To migrate from ExOLEDB, use EWS in Exchange 2010 or the Exchange Web Services Managed API.

 


CDO


  • This technology is available on any computer.
  • CDO wraps MAPI.
  • Commonly used for Outlook experience in applications.
  • CDO was installed with Microsoft Outlook in the past. Since Outlook 2007 this is no longer the case. Instead, CDO 1.2.1 can be downloaded from the Microsoft Website.
  • To migrate from CDO, use EWS in Exchange 2010 or the Exchange Web Services Managed API.
  • CDO 1.21 is not supported and not included on Windows 7 and Windows Server R2.
  • CDO 1.21 can connect to both Exchange 2003 & 2010

 


CDOSYS



  • CDOSYS is available on any Windows based computer.
  • This technology is commonly used to send e-mail messages from applications.
  • For migration:
    • Use the SendItem Operation in EWS in Exchange 2010 or the Exchange Web Services Managed API.
    • In a managed application, you can also use the System.Net.MailMessage class and send e-mail messages via SMTP to your Exchange server.
  • SMTP uses CDOSYS.
  • CDOSYS is in extended support.

 


CDOEX


  • This technology is available only on the Exchange server.
  • CDOEX is deemphasized in Exchange 2007, and deprecated in Exchange 2010.
  • To migrate from CDOEX, use EWS in Exchange 2010 or the Exchange Web Services Managed API.

 


CDOSYS Event Sinks



  • This technology is available only on the Exchange server.
  • CDOSYS SMTP/NNTP event sinks are deprecated in Exchange 2007.
  • CDOSYS SMTP/NNTP event sinks are used to implement ISMTP_OnArrival sinks (via script, for example) and various NNTP sinks.
  • NNTP events are not supported in Exchange 2010.
  • To migrate from CDOSYS SMTP/NNTP event sinks, use transport agents either on the Hub Transport or Edge Transport server.

 


 


Active Directory Services Interfaces (ADSI) or LDAP


  • These technologies are available on any Windows based computer.
  • ADSI and LDAP are commonly used to search the global address list (GAL) and get information about user and contact objects.
  • To migrate from ADSI or LDAP, do the following:
    • To search for a specific user, use EWS in Exchange 2010 (the ResolveNames operation) or the Exchange Web Services Managed API.
    • To browse the GAL, no change is required. EWS does not cover this scenario.

 


Notification APIs


  • Because ICS is part of the Messaging Application Programming Interface (MAPI), the same migration considerations apply.
  • Consider migrating to Event Notifications together with the Synchronization features of EWS in Exchange 2010.
  • EWS provides synchronization support by means of the SyncFolderHierarchy Operation and the SyncFolderItems Operation.

 


Exchange Store event sinks



  • Exchange Store event sinks are available only on the Exchange server.
  • This technology is deprecated in Exchange 2010.
  • To migrate existing Exchange Store event sink applications, use Event Notifications. Event Notifications are part of EWS in Exchange 2010 and the

 


Exchange Web Services Managed API


  • A managed component for the Event Notifications is available on CodePlex. For more information, see Exchange Notifications Component.
  • Synchronous event sinks are no longer supported. Event Notifications are always asynchronous. For this reason, items cannot be modified during a transaction.

 


WebDAV Notifications


  • WebDAV notifications are available on any computer.
  • This technology is deprecated in Exchange 2010.
  • Exchange WebDAV Notifications are the predecessor to Event Notifications in Exchange 2010. Instead of Web Services notifications, HTTP over UDP is used as a communication channel.
  • Applications that use Exchange WebDAV Notifications should migrate to Event Notifications. Event Notifications are part of EWS in Exchange 2010 and the Exchange Web Services Managed API.
  • A managed component for the Event Notifications is available on CodePlex. For more information, see Exchange Notifications Component.

 


SMTP Event Sinks


  • SMTP event sinks are available only on the Exchange server.
  • To migrate from SMTP event sinks, use transport agents either on the Hub Transport or Edge Transport server.

 


CDOEXM



  • CDOEXM is available on any computer that is running the Exchange Administrative tools.
  • CDOEXM is deprecated in Exchange 2007.
  • To migrate from CDOEXM, use Exchange Management Shell cmdlets. These cmdlets are based on Windows PowerShell. You can call Exchange Management Shell cmdlets directly from managed code.

Outlook Address Book Object Wrapper 2003


Outlook Address Book which is scriptable from a Web page currently has no supported replacement.

Leave a Reply

Your email address will not be published. Required fields are marked *


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>