Skip to content

mikes-gh/ews-managed-api

 
 

Repository files navigation

Quick introduction

This is a NET Standard 1.4 port of EWS API. Here are some tips to take into account.

  • NET Framework version is as functional as original
  • Almost all functions involving HTTP requests are now async
  • Outdated async Begin/End functions were removed
  • NET Standard: LDAP Autodiscovery feature will not work
  • NET Standard on Linux: DNS Autodiscovery feature will not work
  • Nuget package can be found here: https://www.nuget.org/packages/Microsoft.Exchange.WebServices.NETStandard/

Getting Started with the EWS Managed API

![Gitter](https://badges.gitter.im/Join Chat.svg)

The 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.

Download options

Download EWS Managed API via nuget.

Getting started resources

See the following articles to help you get started:

Documentation

Documentation for the EWS Managed API is available in the Web services node of the MSDN Library. In addition to the getting started links provided, you can find how to topics and code samples for the most frequently used EWS Managed API objects in the Develop node. All the latest information about the EWS Managed API, EWS, and related web services can be found under the Explore the EWS Managed API, EWS, and web services in Exchange topic on MSDN.

Prerequisites

You need the following to work with the EWS Managed API:

  • A C# compiler to build the DLL files. We recommend Visual Studio 2013.
  • A mailbox on Office 365 or an Exchange server that is running Exchange Online or a version of Exchange starting with Exchange Server 2007.
  • A version of the .NET Framework starting with the .NET Framework 3.5.

Additional resources

Community

Exchange has an active developer community that you can turn to when you need help. We recommend using the Exchange Server Development forum on MSDN, or using the [ews] tag on StackOverflow.