If you're thinking of implementing your own client though, I would strongly advise you to pause and consider whether it's really worth it. As someone who's worked on a server-side implementation of these protocols, I can tell you they can get pretty complicated - and the documentation doesn't always give you enough information. (In some areas it's flat out wrong, too.)
编写一个通过交换活动同步进行通信的应用程序很困难，但并非不可能。 Jons 答案中 Exchange Server 协议的链接包含一个名为 MS-ASWBXML 的文档。你必须自己写一个wbxml的编码器，文档清楚地描述了需求。另外我强烈推荐这个文档：http://www.w3.org/TR/wbxml/
如果低级别工作正常，则必须在 ob wbxml 之上实现 EAS 协议，这并非易事，因为文档中的错误以及不同协议版本的不同行为。这将需要大量的尝试来检查错误，为什么交换服务器不理解您的请求;-)
It is hard, but not impossible to write an app which communicates via exchange active sync. The link to the Exchange Server Protocols in Jons answer contains a document named MS-ASWBXML. You have to write an encoder for wbxml on your own and the document describes clearly the needs. Additionaly I recommend strongly this document: http://www.w3.org/TR/wbxml/
If the low level is working, you have to implement the EAS-protocol on top ob wbxml, which is not trivial, because of bugs in the documentation, different behaviour of different protocol versions. It will be a lot of trial an error to examine, why the exchange server does not understand your requests ;-)
使用 Apple 的内置支持仅意味着使用 Apple 的 API 写入手机上的地址簿和日历存储。您的应用程序不应该知道有关数据同步方式的任何信息：它只是在后台发生。
如果您想直接控制同步过程，那么 Apple 的 API 无法帮助您。 Jon Skeet 的答案包含指向 Microsoft 协议文档的链接，但正如他提到的，您将使自己陷入一个痛苦的世界。
Using Apple's built in support just means using Apple's APIs for writing to the Address Book and Calendar Store on the phone. Your app isn't supposed to know anything about the way that data is synchronised: it just happens in the background.
If you want direct control over the synchronisation process, then Apple's APIs cannot help you. Jon Skeet's answer contains a link to Microsoft's protocol documentation, but as he mentioned you'll be setting yourself up for a world of pain.
EAS 实际上是供设备制造商实施的，而不是供普通应用程序开发的。您应该查看 ActiveSync 协议文档并研究该协议的许可（是的，它是付费许可），然后问问自己是否值得费尽心思编写所有业务逻辑、编码逻辑、密集测试和许可。另一种方法是使用 Exchange Web Services (EWS)，它可能更合适 - 在许多领域更加强大，并且不需要许可。
EAS is really meant for device makers to implement and not normal application development. You should look over the ActiveSync Protocol documentation and look into licensing the protocol (yeah its a pay-for license) and then ask yourself if its worth all the trouble to write all the business logic, ecoding logic, intensive testing and the licensing. An alternative is to use Exchange Web Services (EWS), which might be a much better fit - more rhobust in many areas and no licensing needed.
发布评论
评论（4）
尽管在评论中提出了问题，您可能正在寻找 Exchange Server 协议的 Microsoft 文档。
如果您正在考虑实现自己的客户端，我强烈建议您停下来考虑一下它是否真的值得。作为从事这些协议的服务器端实现工作的人，我可以告诉您它们可能会变得非常复杂 - 并且文档并不总是为您提供足够的信息。 （在某些领域，这也是完全错误的。）
Despite having asked a question in the comment, you might be looking for the Microsoft documentation of the Exchange Server Protocols.
If you're thinking of implementing your own client though, I would strongly advise you to pause and consider whether it's really worth it. As someone who's worked on a server-side implementation of these protocols, I can tell you they can get pretty complicated - and the documentation doesn't always give you enough information. (In some areas it's flat out wrong, too.)
编写一个通过交换活动同步进行通信的应用程序很困难，但并非不可能。 Jons 答案中 Exchange Server 协议的链接包含一个名为 MS-ASWBXML 的文档。你必须自己写一个wbxml的编码器，文档清楚地描述了需求。另外我强烈推荐这个文档：http://www.w3.org/TR/wbxml/
如果低级别工作正常，则必须在 ob wbxml 之上实现 EAS 协议，这并非易事，因为文档中的错误以及不同协议版本的不同行为。这将需要大量的尝试来检查错误，为什么交换服务器不理解您的请求;-)
It is hard, but not impossible to write an app which communicates via exchange active sync. The link to the Exchange Server Protocols in Jons answer contains a document named MS-ASWBXML. You have to write an encoder for wbxml on your own and the document describes clearly the needs. Additionaly I recommend strongly this document: http://www.w3.org/TR/wbxml/
If the low level is working, you have to implement the EAS-protocol on top ob wbxml, which is not trivial, because of bugs in the documentation, different behaviour of different protocol versions. It will be a lot of trial an error to examine, why the exchange server does not understand your requests ;-)
使用 Apple 的内置支持仅意味着使用 Apple 的 API 写入手机上的地址簿和日历存储。您的应用程序不应该知道有关数据同步方式的任何信息：它只是在后台发生。
如果您想直接控制同步过程，那么 Apple 的 API 无法帮助您。 Jon Skeet 的答案包含指向 Microsoft 协议文档的链接，但正如他提到的，您将使自己陷入一个痛苦的世界。
Using Apple's built in support just means using Apple's APIs for writing to the Address Book and Calendar Store on the phone. Your app isn't supposed to know anything about the way that data is synchronised: it just happens in the background.
If you want direct control over the synchronisation process, then Apple's APIs cannot help you. Jon Skeet's answer contains a link to Microsoft's protocol documentation, but as he mentioned you'll be setting yourself up for a world of pain.
EAS 实际上是供设备制造商实施的，而不是供普通应用程序开发的。您应该查看 ActiveSync 协议文档并研究该协议的许可（是的，它是付费许可），然后问问自己是否值得费尽心思编写所有业务逻辑、编码逻辑、密集测试和许可。另一种方法是使用 Exchange Web Services (EWS)，它可能更合适 - 在许多领域更加强大，并且不需要许可。
您还应该看看这个： http://blogs.msdn.com/b/webdav_101/archive/2011/09/29/new-to-exchange-activesync-development.aspx
EAS is really meant for device makers to implement and not normal application development. You should look over the ActiveSync Protocol documentation and look into licensing the protocol (yeah its a pay-for license) and then ask yourself if its worth all the trouble to write all the business logic, ecoding logic, intensive testing and the licensing. An alternative is to use Exchange Web Services (EWS), which might be a much better fit - more rhobust in many areas and no licensing needed.
You should also look at this: http://blogs.msdn.com/b/webdav_101/archive/2011/09/29/new-to-exchange-activesync-development.aspx