Menu
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:
8 Cross-application domain communications
If you need to support communication between objects in different application domains within the same process, you must use .NET remoting.
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:
Clemens, I understand you're on the team that owns both remoting and wcf, and I have a couple of questions that I believe I need to go to the source for.
First, I have a question about whether remoting is going away. Specifically, we have a rather large application that uses remoting extensively for in-process cross-appdomain communication, and I was wondering if this usage of remoting is considered "legacy". If so, will AppDomain.CreateInstance and friends be replaced with something else?
This is his reply:
Remoting is part of the .Net Framework and as such it isn't going away. COM has been in Windows since Windows NT 3.5/Windows 95 and hasn't gone away and I don't see that going away anytime soon, either.
That said, there is very minimal development investment going into Remoting. WCF is the successor of Remoting and supplants COM/DCOM for managed code.
For in-process, cross-appdomain communication Remoting is the CLR's native way of communicating. If you are seeing performance issues pumping larger amounts of data or very many messages in short time, you should take a serious look at WCF and the NetNamedPipeBinding.
814
NET Core and . NET 5 and later versions don't have support for . NET remoting, and the remoting APIs either don't exist or always throw exceptions on these runtimes.
Also, remoting requires runtime support, which is expensive to maintain. For simple communication across processes, consider inter-process communication (IPC) mechanisms as an alternative to remoting, such as the System. IO. Pipes class or the MemoryMappedFile class.
NET Framework will be deprecated. This means you can only use . NET Framework as long as your operating systems (for example Windows Server 2019) still supports it. And with Microsoft shortening its support lifecycles, your operating system end-of-life will come sooner than you may think.
NET is dead as a future framework for web applications and software. Microsoft won't be building for it and they won't support it. But software that already runs on . NET and is no longer being updated will still run on it.
Calling it a legacy technology is a more accurate description.
http://msdn.microsoft.com/en-us/library/72x4h507%28VS.85%29.aspx
This topic is specific to a legacy technology that is retained for backward compatibility with existing applications and is not recommended for new development. Distributed applications should now be developed using the Windows Communication Foundation (WCF).
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.
66
Yes. Remoting is deprecated...and it's official from Microsoft. Here's the link:
.NET Remoting
The first line in the article says in bold:
This topic is specific to a legacy technology that is retained for backward compatibility with existing applications and is not recommended for new development. Distributed applications should now be developed using the Windows Communication Foundation (WCF).
I thought the verbiage was 'deprecated' but apparently they refer to it as 'legacy'
44
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
