Earlier i got a chance to play around creating recurring tasks. I followed the article from MSDN and it worked like charm for me. public TaskType CreateRecurringTask() { // Create the task item and set property values. TaskType task = new TaskType(); task.Subject = "Recurring Task" ; task.Body = new BodyType(); task.Body.BodyType1 = BodyTypeType.Text; task.Body.Value = "Occurs every week" ; task.StartDate = DateTime.Now; task.StartDateSpecified = true ;   // Create the regeneration

We recently found a bug in the way Exchange 2010 calls into your EWS Push Notification endpoint. You may see errors on the Exchange server indicating that it received HTTP 500 errors when calling into your client. Basically, the SOAPAction header is not being sent along with the request. I’ll update this post when this issue is resolved.

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

Recently, I helped a customer with an issue where they were wondering if it was essential to set the ToRecipients , CcRecipients , and BccRecipients if they were setting the same values in the MimeContent property when doing a CreateItem call in Exchange Web Services. While trying to test out the scenarios, I thought “maybe it depends on the order of the elements in your <t:Message>. I soon realized that the order of the properties in the <t:Message> node seemed to matter. As it turns

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

While working with one of my customer we noticed that the yearly recurring appointment doesn’t show in Outlook Web Access or Exchange Web Services(EWS) application. Customer created a monthly or yearly recurring appointment. He set the request to occur on the second, third, or fourth weekday of a month. But, whenever we use Outlook Web Access (OWA) client or customer’s Exchange Web Service (EWS) application to view this request, the request is set to occur on the first weekday of the month; but strangely,

According to our documentation , DeleteItem calls should fail with a ErrorStaleObject error when the ChangeKey is not the most recent one. This, however, is not the case. In Exchange 2007, the ChangeKey is completely ignored in DeleteItem calls. This decision was made on the logic that if you are trying to delete an item, chances are you don’t care if you have the most recent copy or not. But, what if you do? You could try doing a GetItem , check the ChangeKey and then call DeleteItem right after,

One of my customer updated that whenever they try to make the remote Exchange Web Service (EWS) call from his C#.Net 2008 application (VS.Net 2008 - .Net Framework 3.x), he gets the following error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel I had a detailed look at their application code. // Create the Exchange Service Binding ExchangeServiceBinding esb = new ExchangeServiceBinding();   // Add its relevant Credentials like user

In this we will see how to create & send e-mail messages using Exchange Web Service (EWS). It’s pretty simple with EWS to do. // Create the Exchange Service Binding ExchangeServiceBinding esb = new ExchangeServiceBinding(); // Add its relevant Credentials like user name, password, domain and URL esb.Credentials = new NetworkCredential(userName, Password, domain); esb.Url = @"https://myexchangeserver/EWS/Exchange.asmx" ; // CreateItemType and set its relevant properties/values CreateItemType request

If you’re developer who use Microsoft Exchange Web Services to develop client applications, then this is for you to download and play around with it. The Microsoft Exchange Web Services (EWS) Managed API 1.0 Beta 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