I just finished updating a support document which walks through creating a simple COM+ component and ASP.NET page to illustrate how you have to use CDOEXM with ASP.NET due to impersonation limitations of CDOEXM...enjoy... ...Use all code in this...

...We have had a few customers looking for information on writing a custom foreign connector for Exchange 2007 and I finally got around to combining all my information into one document so that I could reuse it. I thought I would share it here as well...

...Sorry I haven't written much lately, I have plenty on the way. Counting down 3 months until my wedding and life just keeps getting busier and busier. Here is a look into the world of a support engineer at Microsoft and some related comments from Raymond...

Here is some exciting news...The Exchange SDK team is blogging now at http://blogs.msdn.com/exchangedev/ ! This a great opportunity to get some direct access to the members of the product team who are responsible for API development and SDK documentation...

Reading this kind of stuff almost makes we wish I was a consultant again...I say almost because then I think about requirement gathering, deadlines, budgets, debating the merits of agile development, etc... The Exchange SDK team linked to this article...

If you have seen the error below when using objects from OOM in .NET 2.0 code then the information that Mason posted recently will explain a lot. The key to avoiding this error is to use the interfaces in OOM not the CoClasses. Mason explains why in his...