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
    .TryGetProperty(
      EmailMessageSchema.DateTimeSent,
      out sentTime);
if (isSentTimeSet)
{
  itemHeader.SentDate = sentTime;
}
Enjoy!

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…