About: Exchange PowerShell Automation

API Type: Exchange Administration API Interface: .NET Framework Class Libraries Business Logic: Managing mailboxes, storage groups, and databases. Language Support: Any .NET language. Direct Property Access: N/A Product Versions: Exchange 2007 and later. Summary:   Exchange PowerShell was introduced with Exchange 2007 as a replacement of CDOEXM and WMI which were used for Exchange administration.   Exchange 2007 did…


About: Extended MAPI

API Type: Mailbox Accessor API Interface: COM-like but not true COM.  MAPI pre-dates COM. Business Logic: Messages and AddressBook, etc. Language Support: Unmanaged C++ only. Direct Property Access: Yes. Product Versions: All versions of Outlook and Exchange versions up to 2003.  Also available for download. Summary: MAPI is the root level API and architecture for the Outlook…


About: CDO 1.21

API Interface: Mailbox AccessorAPI Interface: COM Library with no custom interfaces (IDispatch only)Business Logic: Messages, AddressBook, and default mailbox Calendar.Language Support: Any *unmanaged* COM compatible language (C++, VB6, VB Script).Direct Property Access: Yes.Product Versions: All versions of Outlook and Exchange up to 2003.  Also available for download. Description:   CDO 1.21 (also known as CDO.dll or CDO 1.2.1) is a COM-based (IDispatch…


About: CDO for Windows 2000 (CDOSYS)

API Type: SMTP Sender. API Interface: COM Library. Business Logic: Sending mail via SMTP Language Support: Works with both managed (.NET) and unmanaged code and scripting languages such as VBScript. Direct Property Access: N/A. Product Versions: Windows 2000 and later. Summary: CDOSYS has been a system component used to send email since Windows 2000.  It was meant to replace CDONTS. …

1

Best Practices – What is supported and not.

The issue of supportability comes up a lot.  I would like cover it in this blog post. When we get cases from customers we look at the servers, software and APIs involved.  In addition, the development scenarios and configurations are taken into considerations. A lot of customers run outdated versions of Exchange and Outlook – such as…


EWS Managed API… open source? YES! It’s now Open Source!!!

A few weeks ago the EWS Java API was made open-source.  Last week the EWS Managed API (.NET based) went open source.  So now you can download the code and contribute to it.  You can also directly report bugs on it.  This is another of the wonderful changes which are happening at MS as it…


Getting traces for .NET apps when you cannot modify the application and don’t want to use more than one machine.

One of the biggest pains of .NET applications going against Exchange is getting detailed logs.  Using a tracing tool like Fiddler is great since it will SSL decode traffic, however it won’t capture traffic from a .NET application running on the same box unless that application can set its proxy settings to that of Fiddler.  Having a…

1

Outlook Automation is for People, not for Services.

I don’t know why we see a lot of customers trying to automate Outlook from a service.  It’s pretty well documented that it’s a bad idea.  Outlook Object Model (OOM) was written for automating Outlook for a user sitting at the box running it.   See, Outlook is very personal and I do mean, it’s very,…


Howto: Get Free/Busy Information with WebDAV/HTTP

  CDO 1.21, CDOEX, etc can get Free/Busy information, however WebDAV cannot directly.  You may use a GET against OWA to get this information.    A GET against an OWA URL is really not a WebDAV call… it’s really just plain HTTP GET call – you just need to be sure that the URL is correctly…

1

Howto: WebDAV SEARCH using C#

‘ This example shows how to do a SEARCH using C# // C# Example to SEARCH a mailbox.// TODO://   Add a button and double click on it//   Add a multi-line text box and make it big.//   Add a project reference to System.Xml, an System.Net//   Paste-in the code below//   Do the TODO sections in the code….

2