title: What is the difference between .NET remoting and WCF/TCP for local/LAN communication?
body: <p>OK, so I know that <a href="http://msdn.microsoft.com/en-us/netframework/aa663324.aspx" rel="nofollow noreferrer">WCF</a> is supposed to replace <a href="http://msdn.microsoft.com/en-us/library/kwdt6w2k%28v=VS.100%29.aspx" rel="nofollow noreferrer">dotNET remoting</a>, yet I seem to fail to really grasp if WCF is a full replacement with more options, or if .NET remoting offers some features that are missing from WCF?</p>
  
  <p>As the title hints at, I do not need any of that Web* stuff. The use case is having a C# desktop application expose an RPC-ish interface to make it possible for other programs to communicate with / control the application. Number of possible clients is probably &lt; 10 and communication is exclusively local network.</p>
  
  <p>I found <a href="https://stackoverflow.com/questions/1703720/net-remoting-over-wcf">this question</a> that asks for something similar, but <a href="https://stackoverflow.com/questions/1452268/remoting-or-wcf-for-new-development-between-two-net-apps-on-the-same-machine-u">this other question</a> seems to imply that .NET-remoting can in fact be used in ways that WCF does not offer.</p>