EWS，EWS代理和图表 [英] EWS, EWS proxy and Graph

问题描述

大家好，

我正在寻找有关这些API的更多信息。关于它们以及我们如何使用EWS的几个问题。

在我们的Web应用程序的Web References文件夹中，我们看到了对EWS代理库的引用。该库是否设计为通过代理服务器进行交换？

如果是这样，我正在寻找可能摆脱该API并使用EWS或Graph。目前，我们的应用程序通过URL访问我们的现场交换服务器。它设置了一个交换服务绑定，然后检查电子邮件，并将它们处理到数据库中。
这是一些旧代码，每当电子邮件包含内嵌图像（如签名中的图片）时它就会挂起，然后我们手动将其删除并重新发送。

I我想更新这些代码并以不同方式处理电子邮件。图表是一个可以处理这个问题的更新API，还是我需要坚持使用EWS？ 

解决方案

好的，所以我发现这个链接解释了EWS代理。我到了某个地方。

https://blogs.msdn.microsoft.com/webdav_101/2017/12/15/updating-视觉工作室生成代理类换EWS-发展/

Hi all,

I'm looking for more information on these API's. Just a few questions about them and how we are using EWS.

In our Web References folder of our web application it appears that we have a reference to the EWS proxy library. Is that library designed to work with exchange via a proxy server?

If so, I'm looking into possibly getting rid of that API and going with EWS or Graph. Currently our application reaches out to our onsite exchange server via URL. It sets up an exchange service binding then we check for emails, and process them into a database. This is some old code and it hangs every time the email contains an inline image(like a picture in the signature), then we manually remove it and resend it.

I'd like to bring this code up to date and process the emails differently. Is Graph an updated API that can handle this or do I need to stick with EWS? 

解决方案

Ok, so I just found this link explaining the EWS proxy. I'm getting somewhere.

https://blogs.msdn.microsoft.com/webdav_101/2017/12/15/updating-visual-studio-generated-proxy-classes-for-ews-development/

这篇关于EWS，EWS代理和图表的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！