If you are using InfoStores collection of CDO 1.2.1 for Outlook 2007 to access Public Folder store and not able to get reference to Public Folder store then here is the explanation of the design change in CDO 1.2.1 from SGriffin’s post@ Outlook 2007, Public Folders, MAPI and You . Basically, Outlook 2007's version of the Exchange provider, emsmdb32, doesn't automatically add the Public Folder store to the message store table of a new profile. Instead, it waits until a successful connection has been

If you are developing using Exchange Web Services Managed API then now you can download @ Microsoft Exchange Web Services (EWS) Managed API 1.0 The Microsoft Exchange Web Services (EWS) Managed API 1.0 provides a managed interface for developing client applications that use Exchange Web Services. The EWS Managed API simplifies the implementation of applications that communicate with Microsoft Exchange Server 2007 Service Pack 1 (SP1) and later versions of Microsoft Exchange. Built on the Exchange

Not many people are aware of the feature, but MFCMAPI implements a MAPI Form Viewer . This means MFCMAPI can use MAPI to ask Outlook to display messages. You might have run into this if you ever double-click on a message in MFCMAPI. If you’re on a machine with Outlook installed, the message will open up like it does when you double-click it in Outlook. And if Outlook isn’t installed and you’re using Exchange’s MAPI, you get a scary dialog saying we couldn’t open the MAPI form manager . This is one

We can perform GetItem Exchange Web Service call to get Extended MAPI Properties refer my previous post How to get Extended MAPI Properties in the GetItem Exchange Web Service call? and can also perform FindItem based on the Extended MAPI Properties. In the sample code given below we would use CleanGlobalObjectId to perform FindItem for Calendar Items: NOTE: Following programming examples is for illustration only, without warranty either expressed or implied, including, but not limited to, the implied

Want to make working with Exchange Web Services (EWS) much easier to work with? There is a new API and new tool which can help. No matter which way you are doing or going to be doing EWS calls, you should be familiar with both the Exchange Web Services Managed API and EWSEditor. Exchange Web Services Managed API: The Exchange Web Services Managed API makes life much easier since it wraps a lot of calling code and logic which is needed to successfully execute EWS calls. No matter how you are doing

Matt’s very excited about the release of EWSEditor . This tool does for EWS what MFCMAPI does for MAPI. With this tool, Matt does what I did with MFCMAPI and what I recommend to anyone trying to learn a new API: the best way to learn an API is to write tools that use it. As you work with EWSEditor, you may notice a few things which are similar to MFCMAPI. This is no coincidence. EWS and MAPI, both designed primarily to interact with an Exchange server, share much of the same object hierarchy, which

Over the past year I’ve been working with the new Exchange Web Services Managed API and I have to say, it’s a wonderful thing – especially compared to working with the Visual Studio generated proxy classes for Exchange Web Services.  While working with Exchange Web Services (EWS) early in the Exchange 2007 release it became apparent to me that an editor tool in the spirit of MFCMAPI built on top of EWS might be useful.  At the time I started working on such an editor and based it off the

We can get/set Extended MAPI Properties using Exchange Web Services for Exchange Server 2007/2010. Here is sample code snippet to get value for CleanGlobalObjectID via GetItem call of Exchange Web Services: NOTE: Following programming examples is for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This sample code assumes that you are familiar with the programming language

We had an issue recently where the customer had written an application to process MIME messages that had body parts encoded with the koi8-r charset …or at least that’s what it said: ------_=_NextPart_001_01C9F067.D9742103 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable If you use code similar to the following, the resulting characters returned were not correct. private string ReadBodyPart() { CDO. IDataSource oIDsrc; ADODB. Stream objBpStream = new

As Paul Thurrott notes, we just announced that we’re documenting the PST file structure . I haven’t decided yet if I’ll be writing a standalone parser/viewer/validator, but I’m sure I’ll be adding some interesting stuff to MFCMAPI . I’ll let you know when I know more. digg_url = "http://blogs.msdn.com/stephen_griffin/archive/2009/10/26/inside-the-pst.aspx";digg_title = "Inside the PST";digg_bgcolor = "#FFFFFF";digg_skin = "compact"; digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin