简体繁体 English

.NET Outlook加载项和WCF /进程间通信

[英].NET Outlook Add-in and WCF/Inter-process communication

原文 2010-07-29 13:47:28 1 2 c#/ wcf

I need a tip/advice/recommendation. 我需要小费/建议/建议。

I'm finishing up a Outlook Add-in developed in C#. 我正在完成用C＃开发的Outlook加载项。 I would like this add-in to communication with another application (let's call it Client.exe). 我希望此加载项可以与另一个应用程序通信（我们将其称为Client.exe）。

Client.exe and the add-in will always be running on the same computer. Client.exe和加载项将始终在同一台计算机上运行。 Client.exe is a single instance application. Client.exe是一个单实例应用程序。

What would be the easiest/most convenient way for me to allow the Add-in to communicate with the Client.exe? 对我来说，允许外接程序与Client.exe通信的最简单/最便捷的方法是什么？
Would that be WCF? 那是WCF吗？
Any good resource you can recommend? 有什么好的资源可以推荐吗？

Thanks in advance! 提前致谢！

2 个解决方案

Yes, WCF is probably the way to go. 是的，WCF可能是要走的路。 MS has said themselves that the older .NET Remoting is deprecated in favor of WCF. MS自己说过时的.NET Remoting已过时，而不再支持WCF。 Obviously, the core docs are on MSDN . 显然，核心文档在MSDN上。

This link might help with WCF for IPC in .NET 4.0. 此链接可能有助于在.NET 4.0中使用WCF for IPC。 (IPC = Inter-Process Communication) （IPC =进程间通信）

Yes, use WCF. 是的，请使用WCF。 You can host a WCF service inside of client.exe, and the add-in can call the service. 您可以在client.exe中托管WCF服务，并且加载项可以调用该服务。 You can use any transport, but in your situation could take advantage of named pipes sending binary data. 您可以使用任何传输方式，但是在您的情况下可以利用命名管道发送二进制数据的优势。