Legacy Update: Get back online, activate, and install updates on your legacy Windows PC

This article describes how to migrate an application that uses .NET Remoting to use Windows Communication Foundation (WCF). It compares similar concepts between these products and then describes how to accomplish several common Remoting scenarios in WCF.

• .NET Remoting is a legacy product that is supported only for backward compatibility. It is not secure across mixed-trust environments because it cannot maintain the separate trust levels between client and server. For example, you should never expose a .NET Remoting endpoint to the Internet or to untrusted clients. We recommend existing Remoting applications be migrated to newer and more secure technologies. If the application’s design uses only Http and is RESTful, we recommend ASP.NET Web API. Learn more at ASP.NET Web API. If the application is based on SOAP or requires non-Http protocols such as TCP, we recommend WCF. Learn more at Windows Communication Foundation.This article compares the two technologies and provides recommendations for migrating to WCF.

Files

Status: Live This download is still available on microsoft.com. The downloads below will come directly from the Microsoft Download Center.

File	Size
Migrating from Net Remoting to WCF.docx SHA1: 3359da4622a492e2e9e83a65252835ea4003fecc	55 KB
Migrating from Net Remoting to WCF.pdf SHA1: 9e30c3a71d4affeea9f890057c37ca9c196e3f93	836 KB

File sizes and hashes are retrieved from the Wayback Machine’s indexes. They may not match the latest versions of files hosted on Microsoft servers.

• .NET 4.5.2

• Download this Whitepaper to learn how to migrate your existing .NET remoting code to WCF (Windows Communication Foundation), which will improve the security of your code.