title: Does WCF really replace .NET Remoting?
body: <p>I can understand that WCF is in general better than Remoting, but the two seem quite different to me. MS make this pretty picture to show how great WCF is (or perhaps how poor the other techs are to only check one box each):
  <a href="https://i.stack.imgur.com/0Jvqv.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/0Jvqv.jpg" alt="alt text"></a><br>
  <sub>(source: <a href="http://i.msdn.microsoft.com/dynimg/IC371617.jpg" rel="nofollow noreferrer">microsoft.com</a>)</sub>  </p>
  
  <p>But, WCF is centered around SOA and I don't think it's correct to assume every networked application <em>wants</em> to expose services.</p>
  
  <p>In my case I'm looking at ways to replicate objects between two instances of a server application  on different PCs. WCF appears to just give a modern version of COM... get an object and call methods and it magically calls the version on the other PC. But Remoting appeared to do something quite different and I'm not clear why it was deprecated without being replaced with a similar technology.</p>
  
  <p>So, do MS even claim Remoting is dead? Or do they still support it, acknowledging it has its place <em>alongside</em> WCF?</p>