通过 WCF 进行 .NET 远程处理？
为什么要使用 .NET Remoting 而不是 .NET Remoting wikipedia.org/wiki/Windows_Communication_Foundation" rel="nofollow noreferrer">WCF？
我知道 WCF 有其独特的优势，但是与更现代的 WCF 技术相比，.NET Remoting 能为您提供哪些优势？
Why would you use .NET Remoting over WCF?
I understand that WCF has its distinct advantages, but what advantages would .NET Remoting offer you over the more modern WCF technology?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
通过选择配置 WCF 服务时使用的绑定，WCF 提供了基本上与 .NET Remoting 完全相同的功能。
WCF 从用于实现该服务的传输技术中抽象出服务的概念。您可以定义 WCF 服务，然后通过配置更改用于提供该服务的传输技术，其中之一是 net/tcp，它本质上是 .NET Remoting 使用的技术。
WCF 更像是 .NET Remoting 的替代品，而不是替代品。
WCF provides the ability to essentially do exactly what .NET Remoting does through the choice of binding you use when configuring your WCF service.
WCF abstracts the idea of a service from the transport technology that is used to implement that service. You can define a WCF service and then change the transport technology used to provide that service through configuration, one of these being net/tcp which is essentially the technology .NET Remoting uses.
WCF is more of a replacement for .NET Remoting than an alternative.
WCF 是 .NET Remoting 的替代品。它可以进行基于 HTTP 的传输，也可以进行基于 TCP/IP 的传输，无论是安全的还是不安全的（您可以将任何您想要的序列化引擎插入到 WCF 中），并且更容易定义和维护。
所以我不认为 .NET Remoting 比 WCF 有任何优势，也许它可以帮助您深入了解底层，但为什么要走困难的路呢？
WCF is .NET Remoting's replacement. It can do HTTP based transport and also TCP/IP based tranport, both secure or not secure, (you can plug in to WCF any serializing engine you want) and it's easier to define and maintain.
So I don't think .NET Remoting have anything over WCF, maybe it helps you to go deep and low level, but why go the hard way?