.NET Remoting – 10 Premium Video Tutorials

Here is a collection of 10 premium video tutorials on .NET Remoting by Learn Visual Studio. In order to view the videos, you need to become a member of Learn Visual Studio.

Here are a few things you need to understand about remoting:

• Purpose: .NET Remoting makes it possible for software components to interact across application domains.
• History: .NET Remoting is an API that was introduced with .NET Framework 1.0 in 2002 to improve upon earlier technologies for interprocess communication.
  • In 1990, OLE (Object Linking and Embedding) was developed;
  • in 1993, COM (Component Object Model) was created
  • and in 1997, this was advanced to DCOM (Distributed Component Object Model) and renamed to ActiveX;
  • in 2000, COM+ came into being;
  • in 2002, .NET remoting was introduced;
  • in 2007, WCF technologies were implemented in NET Framework 3.0
• Historical Problems: DCOM had its problems as it relied on proprietary format. Also there were problems of communication between COM objects spread across firewalls. .NET Remoting eliminated these difficulties by supporting various transport and communication protocols and by being adaptable to diverse network environments.
• General Concepts: .NET Remoting allows an application to make an object (which is called a “remotable object”) available across remoting boundaries. This can include different appdomains, processes or even different computers connected by a network. The .NET Remoting runtime hosts the listener for requests to the object in the appdomain of the server application. At the client end, any requests to the remotable object are proxied by the .NET Remoting runtime over Channel objects, that encapsulate the actual transport mode, including TCP streams, HTTP streams and named pipes. As a result, by instantiating proper Channel objects, a .NET Remoting application can be made to support different communication protocols without recompiling the application. The runtime itself manages the act of serialization and marshalling of objects across the client and server appdomains.
• Architecture: See Architecture section of this msdn article on Improving Remoting Performance

.NET Remoting

Series	Title	Date	Presenter	Min
.NET Remoting Series	Introduction to .NET Remoting	1/1/2003	Bob Tabor	27
.NET Remoting Series	Creating a Simple Remoted Component Example	1/1/2003	Bob Tabor	18
.NET Remoting Series	MarshalByReference Server Activated SingleCall	1/1/2003	Bob Tabor	8
.NET Remoting Series	MarshalByReference Server Activated Singleton	1/1/2003	Bob Tabor	6
.NET Remoting Series	MarshalByValue	1/1/2003	Bob Tabor	12
.NET Remoting Series	Configuring Remoted Hosts and Clients	1/1/2003	Bob Tabor	18
.NET Remoting Series	Hosting Remoted Components in IIS	1/1/2003	Bob Tabor	13
.NET Remoting Series	Hosting Remoted Components in a Windows Service	1/1/2003	Bob Tabor	17
.NET Remoting Series	Creating a Remoted Surrogate for a COM+ Serviced Component	1/1/2003	Bob Tabor	23
.NET Remoting Series	Using the SOAPSuds Tool	1/1/2003	Bob Tabor	10