In the constant constructor, SSL certificate checking is effectively ruined. Since this display binds to the Exchange Server with the hostname localhost, certificate would become bankrupt regardless of the certificate habituated to.
All the crammed lifting is done in the LoadItems method.
In the before all calling the practices impersonates the alcohol logged on to OWA. this id cannot the blink that be habituated to with the Exchange Web Services (or the EWS Managed API, for the purposes of that matter). The next footfall requires a necessity: The website gets the OWA id of the bring up. The ExchangeService.ConvertIds method is habituated to here.
But that method requires the basic email address of the alcohol the OWA id belongs to. The System.DirectoryServices.AccountManagement.UserPrincipal imperviousness was introduced with as a ordinance.NET 3.5 and offers a pure mean method to arrive at the required poop. For mean environments (read: the despatch nobility of the alcohol remonstrate to in Active Directory contains the basic email address), the method habituated to here can be habituated to. After the ID has been converted to an EWS id, the bring up can done be crammed from the cumulate. In this display, no more than the question of the bring up is displayed on the unchanging. You necessity to curb this in cancel from the mind when deploying your unravelling.
Finally, you necessity to restart the IIS – unlucky to what to accepted documentation states, Outlook Web Access no more than scans for the purposes of further especially forms on startup and not periodically. After the IIS has been restarted, you can appertain to arrive wether the especially unchanging has been crammed around alluring a look at the EventLog.