.NET Remoting over WCF?

Question

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?

Answer 1

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?

Answer 2

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.