| .NET Remoting ( A Simple Approach) |
| C# Help |
| .NET Remoting provides a powerful and high performance way of working with remote objects. Architecturally, .NET Remote objects are a perfect fit for accessing resources across the network without the overhead posed by SOAP based WebServices. .NET Remoting is easier to use than Java's RMI, but definately more difficult than creating a WebService. In this article, we will create a remote object that will return rows from a database table. For the sake of simplicity i have used the NorthWind database that is packed with the installation of the Microsoft SQL Server. |
|
| .NET Remoting - The Interface Approach |
| C# Help |
| In this article, we will create a remote object, and access this object using an interface. This method is important when creating a physical separation between business tier and consumer code. In traditional Remoting approaches, to access a remote object, you need a copy of that object on the client machine. With this approach, the metadata is split into a separate library that can be copied to the client machine. |
|
| Adventures in Visual Basic .NET: Broadcasting Messages to Multiple Clients |
| MSDN |
| Rocky Lhotka discusses optimistic concurrency and shows you how to create a messaging system that lets multiple users know when they are editing the same data at the same time. |
|
| An Introduction to Microsoft .NET Remoting Framework |
| MSDN |
| This article explains the fundamentals of the Microsoft .NET Remoting Framework. In addition to describing the main components that make up the .NET Remoting Framework, this document describes different scenarios in which .NET Remoting could be used to communicate with distributed objects. |
|
| BUG: "Unable to import binding" error message when you try to create an XML Web service proxy for the .NET Framework remoting service that contains Char data type members or Guid data type members |
| http://www.kbalertz.com/ |
| (831689) - Describes the "Unable to import binding" error that occurs when you try to build XML Web service proxies for the .NET Framework remoting services that contain Char or Guid data type members. Requires familiarity with the .NET Framework remoting. |
|
| Creating a .NET Assembly Listener for Remoting |
| C#Today |
| A web service to most is a business object that is hosted on a web server and exposes a set of methods and instructions to use those methods. However some organizations see a web server such as IIS as a perceived risk and want to protect their business logic on an application server. In this article Tim Heuer examines a way around that problem, by introducing .NET remoting. Remoting introduces the same benefits as DCOM does with interprocess communication across computer boundaries, but enables us to allow our remoted objects to reside outside IIS and yet still service SOAP requests to a simple business component over HTTP. |
|
| Format for .NET Remoting Configuration Files |
| MSDN |
| All remote objects have to be registered with the Remoting Framework before clients can access them. During this registration process, the Framework is provided with all the information required to activate and manage the lifetime of the object. The most important pieces of information required for registration is the type of the object, the URI where it will be deployed, the activation requirements for managing the object lifetime and the channels that can be used to connect to this object. |
|
| Marshalling By Reference First steps |
| Dot Net Dan |
| For the first remoting app we build, everything we do will be explicit in the code. No config files or IIS setup required. |
|
| Remoting and XML Web Services in Visual Basic .NET |
| MSDN |
| Since the introduction of DCOM support in Visual Basic 4.0, I've been on a continual quest to find the best ways to design and build distributed applications using Visual Basic. With Visual Basic .NET, my quest has moved to a whole new level. Gone are the days of struggling with DCOM and firewall security administrators who, for their own nefarious purposes, refuse to open hundreds of ports to the world at large. The .NET Framework provides us with two solutions that can be used to provide DCOM-like functionality without all those headaches. Both Web services and Remoting are large topics by themselves. In this column, we'll take a high level look at how to use both technologies from Visual Basic .NET to return an object's data. |
|
| Side-By-Side and Versioning Considerations for .NET Remoting |
| MSDN |
| Developers building distributed applications must know how to ensure that applications can run side-by-side using different versions of the Common Language Runtime (CLR) and how to deal with strong-named assemblies when deploying distributed applications using remoting. This article provides a brief overview of the implications that versioning has on a distributed application by examining activation, method calling, and serialization in this context. |
|
| Tie Into Remote Objects |
| .NET Magazine |
| One advance that's part of the .NET architecture is .NET Remoting—an object-oriented, extensible framework that enables distributed application development. You can use .NET Remoting and C# to your advantage in distributed apps, particularly in implementing design patterns. |
|
| Understanding .NET Remoting |
| C#Today |
| The .NET remoting infrastructure is the core facilitator for communication between multiple app domains in the .NET framework. Exposing your .NET objects as web services is extremely simple using the remoting framework and yet it gives you all the power and flexibility to fine tune the performance of your Web services to meet specific customized business processing needs. In this article, Aravind Corera examines the individual building blocks that constitute the .NET remoting framework such as the hosting environments, transport channels, serialization formatters, lifetime management and activation policies and shows you how to put these pieces together to build scalable, reliable and high-performance web services. |
|
| Using Remoting Callbacks |
| The Code Project |
| This article describes how to implement an asynchronous remoting callbacks from different remote objects such as .Net Service (COM+), Web Service and classic .Net object using the C# language. |
|
| Writing a Messenger Application Using C# - Part 1 |
| C#Today |
| A messenger application provides users with a simple way to communicate instantly with each other. This article covers an approach to writing a sample realtime chat messenger application, much like the existing ones like MSN, Yahoo, AOL etc using C#. In this first part of this article, Saravana Kumar covers the data model, the core functionality assembly, the server, and how it is configured using .NET remoting to expose it to remote clients. The second part of the article will cover the client applications. |
|
