Migrating from .NET Remoting to WCF
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.
Important! Selecting a language below will dynamically change the complete page content to that language.
Version:
1.0
Date Published:
7/15/2024
File Name:
Migrating from Net Remoting to WCF.pdf
Migrating from Net Remoting to WCF.docx
File Size:
899.9 KB
57.5 KB
.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.Supported Operating Systems
Windows 7, Windows 8, Windows 8.1, Windows Server 2003 Service Pack 2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows XP Service Pack 3
.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.