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

//====================================================================================================== // CdoexmMailboxUtil - // Exchange Mailbox and user account creation sample. // // This sample demonstrates the following: // Creating a user account in AD // Mail Enable an existing user. // List information on an existing user. // Note: This code is provided as a sample only, so you need to test and take responsibility // of the code and any of its possible actions before usage. Being a sample,

If your living in a pre Exchange 2007 Powershell worlds and want to mail enable or disable public folders, you may come to the point where you will be needing to write some CDOEX and CDOEXM code to do what you want. Below is a C# sample console application which will allow you to mail enable, mail disable and view mail settings on a public folder. //====================================================================================================== // ExchangePfUtil - // Exchange Public Folder

Hmmm, there are very few samples on setting multiple extended properties on folders using a POST to EWS... so, I thought I would blog one. This sample can be used with: http://blogs.msdn.com/webdav_101/archive/2009/02/27/howto-post-xml-to-ews-using-exchangeservicebinding-credentials.aspx Note the following: The version is set. Each property being set is done under a separate SetFolderField node. <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

I thought it would be fun to blog another sample of getting a list of attachments using EWS. So, here is a handly method for populating a list of attachments. // ----------------------------------------------------------------------------------------- // GetFileAttachmentsListLv // Sets a listview to the attachments on an item. // Returns number of attachments. // ----------------------------------------------------------------------------------------- public static int GetFileAttachmentsListLv(

Customers sometime have a misunderstanding of what is covered when supported is provided. So, I’ve put together a link covering common areas for all to read. I would suggest starting with the link below to get an understanding on what is supported to understand some of the basics of supportability. OFF: Getting Support for Microsoft Office Solutions http://support.microsoft.com/default.aspx?scid=kb;EN-US;234322 Incidents: Here is some info on what is supported as far as incidents – ie break-fix.

I’ve run into issues with using a GET to read large attachments using HttpWebRequest. Because of this, I use System.Net.WebClient instead. Big attachments will have an error thrown back with HttpWebRequest, however it’s possible to GET the smaller ones. So, since System.Net.WebClient seems to work just as good, I use it for getting attachments. I use HttpWebRequest for everything else. Public Function SaveAttachmentToFile(ByVal sUri As String, ByVal sFileName As String) As Boolean Dim bRet As Boolean

I thought I would share some simple sample code which is useful for finding problems in string content. Here are three methods I wrote which are useful to see whats in a string and differences between strings. I use these with a simple program which uses two text boxes for pasting text into and a third window for displaying results. Please note that I'm not using stringbuilder here on purpose - I do avoid it when writting code which i want to be as simple and language generic as possible (I would

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 formatted. Most OWA URLS being called in this manor are not supported, however this is one of the few exceptions. Here are some things to be aware of: · Free/Busy information is stored in the public store under the NON_IPM_SUBTREE

The DELETE verb only works on Exchange 2003 SP1 - it will not work on any earlier version/service pack. CDOEX, CDO 1.21, Extended MAPI, etc can do this on Exchange 2000 or 2003. One possible work-around is to read the message stream using a WebDAV GET, modify the stream to remove the attachment and then do a PUT to write it back. You will want to watch-out to be sure that you do not lose any custom properties which you have set. Also, you may use an unsupported OWA command to delete the attachment