Microsoft Exchange via CDOEX - Part 1

Why does Exchange 2000 suck for this? You have to use some of the COM libraries

Exchange 2007 won't have any issues since it will expose some WebServices from what I've read and heard.

The libraries needed to interact with Exchange2000 from .NET aware languages to my knowledge are:
  • Microsoft ActiveX Data Objects 2.5 Library
  • Microsoft CDO for Windows 2000 Library
My dislikes to this approach:
  • Not very clean to use
  • The COM Object hangs if you try to re-connect/re-access Exchange
    • I'd like to know if anyone out there has this happen to them, I might just be doing it wrong?
To remedy the hanging issue -- I implemented a static MailServerFactory.Create() method which created an AppDomain (thanks to my friend Thomas for making this suggestion) to run the Exchange2000 class in . This Exchange2000 class had the calls/creation of all the CDOEX objects and it works GREAT. Of course, the Exchange2000 class had to inherit from MarshalByRef to get through the remoting proxies across AppDomains.

Definitely more information will be posted for the next few parts.