EWS Client Development in Exchange 2010
Last modified: October 14, 2009
Applies to: Exchange Server 2007 | Exchange Server 2010
Exchange Web Services uses standard industry protocols that provide interoperability between heterogeneous servers and client applications. SOAP XML messages provide the communication between the computer that is running Microsoft Exchange Server 2010 and Web services client applications.
This section provides information about two ways to create client applications that consume Exchange Web Services:
For Exchange 2010 and later versions, we strongly recommend that you use the Microsoft Exchange Web Services (EWS) Managed API instead of auto-generated proxies for developing against Exchange Web Services. The EWS Managed API object model is significantly easier to use than auto-generated proxy object models.
Note
Before you start to develop an Exchange Web Services client application, review the setup and configuration information that is provided in the Microsoft Exchange Server 2010 Help. Depending on the configuration of your Exchange organization and the location of the clients, you might have to configure some settings before you can access the appropriate Exchange 2010 computer that has the Client Access server role installed.