Microsoft Office 365, Exchange Developer : How to include EWS Managed API via NuGet in your Visual Studio solution?

As you aware Exchange Web Services (EWS) Managed API provides a managed interface for developing .NET client applications that use EWS. By using the EWS Managed API, you can access almost all the information stored in an Office 365, Exchange Online, or Exchange Server mailbox – on-premises starting from Microsoft Exchange Server 2007, 2010, 2013,…


FYI: Microsoft Exchange Server 2007 & end of support next year…

Yes you heard it right, Microsoft Exchange Server 2007 is approaching the end of support by next year; you can refer the Support lifecycle for it. Customers who are using Exchange Server 2007 for any of their email and calendar services should begin planning to move the associated mailbox data and resources to Office 365…


Error: After Office 2016 upgrade Outlook 2016 fails to connect Exchange Server 2007

After upgrading to Outlook 2016 for Windows fails to connect Exchange Server 2007 mailbox and you get the following error message.  Also when you open Outlook, you get error message that Outlook can’t open your data files. These errors occur because Outlook 2016 for Windows doesn’t support Exchange Server 2007 and earlier versions. In such…

2

Supportability matrix for Microsoft Exchange Server 2007, 2010 and 2013 versions

The Exchange Server Supportability Matrix provides a central source for Microsoft Exchange administrators to easily locate information about the level of support available for any configuration or required component for supported versions of Microsoft Exchange. You can refer the supportability matrix here – all of them documented in a single place. It talks about Release…


Microsoft Support Lifecycle for Exchange Server family – Exchange Server 2003, 2007, 2010 & 2013

Visit the below Microsoft support lifecycle policy page to view Microsoft’s guidelines for product support from availability to end of product support lifecycle. I had added the support lifecycle policy information for the Exchange Server family of products. Exchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 For example, I enclosed Exchange…


December 2014 – Exchange Server releases (Exchange Server 2007, 2010, 2013)

This December we had released the following releases – it releases include updates for Exchange Server 2013, 2010, and 2007. The following packages are now available on the Microsoft download center. Exchange Server 2013 Cumulative Update 7 UM Language Packs for Cumulative Update 7 Exchange Server 2010 SP3 Update Rollup 8 Exchange Server 2007 SP3…


Getting started with EWS Java API

As you know the EWS Java API, a java client library to access Exchange Web Services (EWS) – a SOAP-based API and you can use it from Java or any other language that lets you POST XML data over HTTP. The API works against Office 365 Exchange Online as well as on premises Exchange Server….

2

MAPI: How to programmatically get autocomplete cache/entries for OWA 2013?

In continuation of my earlier post, I got few additional queries how to programmatically (using MAPI) get autocomplete cache/entries for OWA 2013. I used latest MFCMAPI as a code sample to achieve this. Download latest MFCMAPI from http://mfcmapi.codeplex.com Select “Session” Menu > Select “Logon” > select profile > Open the “store” > select  “Root Container”…

2

Feature comparison: EWS vs. EWS Managed API

Are you a .Net Developer who develop custom application using Exchange Web Services (EWS) Managed API or EWS (Auto-generated proxies)? Then this is for you. The EWS Managed API provides an intuitive interface for developing client applications that use EWS. The API enables unified access to Exchange resources, while using Outlook–compatible business logic. In short,…

1

Download: 101 samples for Exchange Server 2013

Now you can download the 101 Exchange Web Service samples to download them all, or select the samples that you want and download them individually. This pack includes 101 code samples that show you how to develop Exchange 2013 solutions. The code samples in the Exchange 2013: 101 code samples package show you how to…

1

More articles on Exchange Client throttling…

To get more information on Client Throttling policies, you can refer the following articles: General information about client throttling policies More Throttling changes for Exchange Online Exchange Online EWSMaxSubscriptions throttling budget calculation  EWS Throttling in Exchange Online Effects of Throttling on your Deployment in Exchange 2010 SP1 EWS best practices: Understand Throttling policies Exchange Server…


Exchange throttling: MAPI application fails with error “The information store could not be opened. [MAPI 1.0 – [MAPI_E_LOGON_FAILED(80040111)]]”

We recently resolved a case where a customer tries accessing Exchange Server 2010 mailboxes (DAG) via their custom Exchange MAPICDO based application. On average 2-3 days once, they’re frequently facing an error “The information store could not be opened. [MAPI 1.0 – [MAPI_E_LOGON_FAILED(80040111)]]” while attempting to connect to Exchange server 2010. After some days of…


Download: Exchange Web Services (EWS) Managed API 1.2.1

Now, you can download the latest Exchange Web Services (EWS) Managed API 1.2.1 (version 14.03.0067.001) @ two flavors – 64-bit, 32-bit. It provides a managed interface for developing client applications that use Exchange Web Services.  The latest EWS Managed API 1.2.1 includes new Exchange Web Services (EWS) client logging features for Exchange Online as part…


Exchange Developer: Exchange Web Services – Best Practices (Part 2)

In Part 2, Matt discusses about searching, notifications, synchronization, and patterns when working with Exchange Web Services. The two part series would be good one for those who’re involved in building custom applications using Exchange development/Exchange Web Service. Enjoy!!