问题描述
每个人都在说如何.NET Remoting的被替换为WCF，但我不知道是多么准确的是。我还没有看到远程正在去precated任何官方消息，而且在我看来，有一定场景中远程更有意义比WCF。无远程处理有关的物体或方法都已经去precated，即使是在4.0版本的框架。这也是我的理解是System.AddIn在3.5和4.0的框架使用远程处理。
没有人有任何官方消息相反的？
在文章中，选择在.NET 通信选项（ 3.0，因为这是该条款的最新版本），它规定：
现在，当然，这是不准确的，因为WCF当然是可以用来跨AppDomain的界限，但它给了该方案的正式建议？
更新：我给克莱门斯Vasters（谁是拥有远程处理和WCF团队）这个问题：
这是他的回复：
称它是传统技术是一种更准确的描述。
http://msdn.microsoft.com/en-us/library/72x4h507%28VS.85%29.aspx
更新：WCF没有外部/内部/工艺/外部/内部AppDomain的区分。如果您在使用WCF台计算机通信使用命名pipes-使用它应该给几乎所有现实的情况不错的表现。
有关各种分布式通信技术的性能比较看到这里。
Everyone is saying how .NET Remoting is being replaced by WCF, but I'm wondering just how accurate that is. I haven't seen any official word that Remoting is being deprecated, and it seems to me there are certainly scenarios where Remoting makes more sense than WCF. None of the Remoting-related objects or methods have been deprecated, even in version 4.0 of the framework. It is also my understanding that System.AddIn in the 3.5 and 4.0 frameworks use Remoting.
Does anyone have any official word to the contrary?
In the article, Choosing Communication Options in .NET (for 3.0, as that's the latest version of that article), it states:
Now, that, of course, isn't accurate, as WCF can certainly be used to cross appdomain boundaries, but is it giving the official recommendation for that scenario?
Update: I sent Clemens Vasters (who was on the team that owns Remoting and WCF) this question:
This is his reply:
Calling it a legacy technology is a more accurate description.
http://msdn.microsoft.com/en-us/library/72x4h507%28VS.85%29.aspx
Update: WCF doesn't distinguish between inter/intra/process/inter/intra-appdomain. If you are using single machine communication in WCF you use named pipes- using it should give good performance in virtually all realistic scenarios.
For a performance comparison of various distributed communication technologies see here.
这篇关于是.NET Remoting的真的去precated？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！