Skip to main content

EWS - Get Items from 'Draft' folder " This property was requested, but it wasn't returned by the server"

This is a blog post dedicated for people that are working with Exchange Web Server Library (EWS). This is wrapper over EWS API that gives the possibility to a developer to interrogate and communicate with an Exchange Server.
When we are loading the list of emails from a folder we would have the following code:
ExchangeService service = ...
string folderId = ...
ItemView itemView = ...
Folder folder = Folder
  .Bind(service, new FolderId(folderId));
FindItemsResults<Item> items = folder
  .FindItems(searchFilter, itemView);
We get a list of ‘Item’ that we can manipulate by us. It is very easy to extract different email details like ‘Subject’, ‘Id’ or ‘SentDate’.
This solution will works for 99% or the cases, except one. When we want to load the items from ‘Draft’ folder. Surprise, we don’t have the ‘SentDate’ set. Of course this is normal, but EWS library will throw an ugly exception.
Item item = ...
DateTime sentDate = item.DateTimeSent;
What should we do for this case?
Well, the solution is pretty simple. We don’t need to access this property directly, using ‘DateTimeSent’ property. ‘TryGetProperty’ needs to be used in this case. This method give us the possibility to check if a property was set. It is similar with ‘TryParse’. The only difference is that we need to specify what property we want to get.
Each entity type was a XXXSchema class, where all the properties are defined. In our case, to be able to manage this case, we should have the following code:
DateTime sentTime;
bool isSentTimeSet = item
      out sentTime);
if (isSentTimeSet)
  itemHeader.SentDate = sentTime;


  1. Great article, just what I wanteed to find.


Post a Comment

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…