For those situations where Web Services doesn't provide the flexibility or is too verbose for optimal data communication, Microsoft introduced .NET Remoting which allows a pluggable and customizable cross application/computer/platform communication mechanism. This series thoroughly discusses how to add .NET Remoting to your applications.
The following videos are available for this series:
| Introduction to .NET Remoting | |
| Narrated PowerPoint slides explaining the basic concepts of .NET Remoting. | |
| Creating a Simple Remoted Component Example | |
| Demonstrates the most basic remoted component example I could think of. Will use this as a basis for the rest of the videos in this series. | |
| MarshalByReference Server Activated SingleCall | |
| Demonstrates creating a MarshalByRef component that is Server Activated (server instance created when the client creates a proxy) of Activation Type SingleCall (server instance abandoned after call). | |
| MarshalByReference Server Activated Singleton | |
| Demonstrates how to modify the previous video's example to more statefully host a remoted component. | |
| MarshalByValue | |
| Demonstrates how to create a remoted object that serialized and marshalled by value to the client. | |
| Configuring Remoted Hosts and Clients | |
| Demonstrates how to save channel, location and other remoting settings for both Client and Host applications in special XML Configuration files used by the Remoting classes. Also demonstrates the use of the .NET Framework Configuration Tool to change settings from a GUI. | |
| Hosting Remoted Components in IIS | |
| Demonstrates how host an object as a remoted component in IIS, the appropriate settings in the Web.config, and how to configure the client to access that component. Additionally, talks about when it makes sense to use IIS as a hosting mechanism for your remoted components. | |
| Hosting Remoted Components in a Windows Service | |
| Demonstrates how to host a remoted component in a Windows Service. Also provides an overview of the pros and cons of the different hosting options for remoted components. | |
| Creating a Remoted Surrogate for a COM+ Serviced Component | |
| Demonstrates how to build a COM+ Serviced Component then host it in Component Services. Then, we create a remoted component that acts as a surrogate for a client on a remote machine. | |
| Using the SOAPSuds Tool | |
| Demonstrates how to use the SOAPSuds tool to create a proxy with metadata about a components types so that the client application can early bind to that proxy. |
Home: http://www.learnvisualstudio.net/content/series/dotnet_remoting_series.aspx
Link download :
dotnet_remoting_series.rar
http://rapidshare.com/files/219506712/dotnet_remoting_series.rar
Password default : booktraining.net
No comments:
Post a Comment