.NET Remoting – 10 Premium Video Tutorials





Here is a collection of 10 premium video tutorials on 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 () 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

SeriesTitleDatePresenterMin
.NET Remoting SeriesIntroduction to .NET Remoting1/1/2003Bob Tabor27
.NET Remoting SeriesCreating a Simple Remoted Component Example1/1/2003Bob Tabor18
.NET Remoting SeriesMarshalByReference Server Activated SingleCall1/1/2003Bob Tabor8
.NET Remoting SeriesMarshalByReference Server Activated Singleton1/1/2003Bob Tabor6
.NET Remoting SeriesMarshalByValue1/1/2003Bob Tabor12
.NET Remoting SeriesConfiguring Remoted Hosts and Clients1/1/2003Bob Tabor18
.NET Remoting SeriesHosting Remoted Components in IIS1/1/2003Bob Tabor13
.NET Remoting SeriesHosting Remoted Components in a Windows Service1/1/2003Bob Tabor17
.NET Remoting SeriesCreating a Remoted Surrogate for a COM+ Serviced Component1/1/2003Bob Tabor23
.NET Remoting SeriesUsing the SOAPSuds Tool1/1/2003Bob Tabor10


 

Related posts:

  1. ADO.NET – Over 3 Hours of Premium Video Tutorials Here is a collection of over 3 hours of premium...
  2. ASP.NET Video Tutorials – (35 Hours Premium Videos) Here is a collection of over 35 hours of premium...
  3. .NET Framework Threading – 5 Premium Video Tutorials Here is a collection of 5 premium video tutorials on...
  4. C# Video Tutorials (26 Hours of Premium Videos) Here is a collection of over 26 hours of premium...
  5. .NET Framework – 4 Premium Videos by Learn Visual Studio Here is a collection of 4 video tutorials on .NET...

Related posts brought to you by Yet Another Related Posts Plugin.

Speak Your Mind

Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!

This blog uses the cross-linker plugin developed by Web-Developers.Net