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

“What is the best way to deploy VSTO add-ins for Outlook?” This is one of the most common question asked by our customers who are developing add-ins using Visual Studio Tools for Office(VSTO) for Outlook and other Office Applications.  Simple answer is that it’s all depend on you requirements and environment. We can opt for either ClickOnce Deployment or Windows Installer. We can refer to Choosing a Deployment Strategy and the following table compares the features of ClickOnce deployment with

Microsoft introduces “Click-To-Run” technology for downloading trial and purchasing. For people who want to try or buy Office 2010 on existing PCs, Microsoft is unveiling Click-to-Run, a new and enhanced download experience for consumers. Benefits : Click-to-Run makes it easier than ever for customers to try or buy Office digitally by significantly reducing the time and effort required to download Office 2010 over the Internet. Click-to-Run automatically downloads and installs any software patches

This is a continuation of my previous post . I wanted to take a moment and discuss the intent of the sample, how to get it working, and some caveats when you attempt to take the sample and turn it into production ready code. Purpose The purpose of the sample is to demonstrate how to use Remote Powershell from several different clients and then call an Exchange 2010 cmdlet. Components There are several components that make up the sample, the RemoteExchangePS proxy DLL, the managed client and the native

I have seen this question posed a lot so I decided that I would post a quick code sample here and the complete sample on my samples site. In my sample I created a managed client and a native client which both call into a managed DLL that runs the Get-ExchangeServer cmdlet using Remote Powershell. Here is the method that actually does the work if you don't want to download the entire sample: private const string SHELL_URI = " http://schemas.microsoft.com/powershell/Microsoft.Exchange "; public void

From the Exchange Team blog : “Today we released an updated version of the Exchange Remote Connectivity Analyzer . For those of you not familiar with this site, it is a Web-based tool that helps you troubleshoot connectivity issues. The tool simulates several client logon and mail flow scenarios. When a test fails, many of the errors have troubleshooting tips to assist you in correcting the problem. For more information, see our previous blog post here . … Additional tests Exchange Web Services -

Congratulations to the Exchange product team, Exchange 2010 has been released to manufacturing. http://msexchangeteam.com/archive/2009/10/08/452775.aspx

I have been working lately with this customer who was trying to create new signature files under %APPDATA%\Microsoft\Signatures folder which will be used by Outlook 2007 (SP2) but what we discovered is that whenever they try to use it, it used to crash Outlook. This was the content of the HTML Signature file that we were using. < HTML > < BODY > < IMG SRC ="http://www.server.com/logo.jpg" /> </ BODY > </ HTML > .csharpcode, .csharpcode pre { font-size: small;