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

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

“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

I recently had a case where a customer was asking how to figure out the mailbox version of a given user using Exchange Web Services (EWS). We noticed there is a node returned in the AutoDiscover response message called ServerVersion, but this value seems pretty opaque. Here’s a snippet from the AutoDiscover POX response from my test server: < Protocol > < Type > EXCH </ Type > < Server > MAILBOXEX7.domain.com </ Server > < ServerDN > /o=First Organization/ou=Exchange

There are new enhancements to SMTP support for .NET 4.0 - in the area of Unicode support and increased standards compliance, which is an important aspect in ensuring that legitimate emails do not get flagged as spam, as well as a few other useful features. + Decreased likelihood of being accidentally flagged as spam + Increased Unicode support + Clarification on setting header values + Multiple Reply-To addresses with the new property ReplyToList + Content Disposition time zones + Mail Address formats

Matt , Rick , and I were working on an issue recently where when an application using EWS would set a contact’s Street address to a value containing a carriage return and line feed, like this: physicalAddress.Street = "1234 56 Ave NE\r\nc/oPatrick Creehan" ; the address card control in Outlook would render it like this: Ugly, right? The problem was that the XMLSerializer would strip out the line feed and leave the carriage return, which the address card didn’t like. We could prove by sending

In continuations of my previous post How to do FindItem and GetItem Operations of Exchange Web Services using VB.net ; Here is the Exchange Web Services sample in VB.net to perform following task: FindFolder (How to perform FindFolder Operation to get FolderId of specific folder for the root of the mailbox) MoveItem (How to perform MoveItem Operation to move an item to the another folder within the mailbox) NOTE: Following programming examples is for illustration only, without warranty either expressed

In this article, we are going to see how we can get Explorer & Inspector selected mail item using Outlook Object Model (OOM) & .Net and process it. '[Code Snippet : VB.Net, .Net Framework 2.0/3.5, Outlook Object Model (OOM)] ... 'Declaration part Dim ThisOutlookSession As Outlook.Application = New Outlook.Application Dim NS As Outlook. NameSpace = ThisOutlookSession.Session Dim objsel As Object 'Check it's Inspector or Explorer Window If TypeName(ThisOutlookSession.ActiveWindow) = "Inspector"

It does seem to be a bit of a dearth of VB.net samples for Exchange Web Service. So here is a sample Vb.net code which demonstrates: FindItem (How to perform FindItem Operation to list all items from the inbox folder of a use mailbox) GetItem (How to perform GetItem Operation to get an item with all properties) 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