Is .NET Remoting really deprecated?

Calling it a legacy technology is a more accurate description msdn.microsoft.com/en-us/library/72x4h50... 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.

Calling it a legacy technology is a more accurate description. msdn.microsoft.com/en-us/library/72x4h50... 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.

It seems to me that remoting still has a place in cross-appdomain communication (AppDomain. CreateInstanceFromAndUnwrap and friends). – Mark Aug 18 '09 at 15:30 Yes it is.

If these classes had been "deprecated", they would have the ObsoleteAttribute applied to them- msdn.microsoft. Com/en-us/library/system. Obsoleteattribute.aspx.

– RichardOD Aug 18 '09 at 15:47 1 @Mark, @RichardOD: The article is the head article on . NET Remoting.It does not just refer to inter process communication. Also, the fact that the ObsoleteAttribute is not on them in .

NET 3.5 means nothing, since the decision to announce Remoting (and ASMX web services) as "legacy" was made post . NET 3.5 RTM. – John Saunders Aug 18 '09 at 16:11 @John: They're not marked Obsolete in 4.0 either (at least not yet).

– Mark Aug 18 '09 at 16:22 @Mark: you mean 4.0 beta 1. – John Saunders Aug 18 '09 at 16:50.

Yes. Remoting is deprecated...and it's official from Microsoft. Here's the link: .

NET Remoting I thought the verbiage was 'deprecated' but apparently they refer to it as 'legacy.

11 IMO 'deprecated' is stronger than 'legacy': 'legacy' means "don't start", and deprecated means "if you've already started, stop now, because it may be removed entirely in future versions". – ChrisW Aug 18 '09 at 15:29 So, would it be accurate to say it's been deprecated for cross-application communication, but not for cross-appdomain communication? – Mark Aug 18 '09 at 15:31 1 @Mark: I don't read it that way.

WCF seems as applicable for intra-process communication as is Remoting (see the NetNamedPipeBinding in WCF). – Michael Petrotta Aug 18 '09 at 15:37 1 @Mark: Regardless, Remoting is deprecated. @ChrisW: I doubt that Remoting will be removed in the near term, but you can expect fewer bug fixes, if any, and less support, if any.

– John Saunders Aug 18 '09 at 16:05 1 @Mark - what is your real question? Remoting is considered legacy technology. It sounds like you don't wish that to be true.

You may have good reasons, but that doesn't really speak to Microsoft's current recommendations. – Michael Petrotta Aug 18 '09 at 16:19.

Clemens Vasters, the Technical Lead for the Microsoft . NET Service Bus (that means both Remoting as well as WCF) talks about WCF vs. Remoting in this forum post. To summarize the post he ends up recommending WCF over Remoting.

I'm not sure if . NET 4.0 uses remoting internally but you could try sending Clemens the question... I'm sure he knows the answer.

Shocking. – quillbreaker Aug 18 '09 at 16:06 9 In what way is WCF not compatible with everything else? And Remoting was compatible with what?

– John Saunders Aug 18 '09 at 16:13 1 If you're looking for compatibility, WCF is the -only- choice (except asmx, of course, but that's "legacy" as well). Remoting was -never- suitable for scenarios where compatibility was a requirement. – Mark Aug 18 '09 at 16:48 1 I took your suggestion and asked Clemens.

S reply: "Remoting is part of the . Net Framework and as such it isn't going away... For in-process, cross-appdomain communication Remoting is the CLR's native way of communicating." – Mark Aug 18 '09 at 17:11 He goes on to say that you should "take a serious look at WCF and the NetNamedPipeBinding. " – John Saunders Aug 18 '09 at 20:57.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.