| .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. |
|
| 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. |
|
| COM+ and .NET - A practical approach - Part 3 |
| The Code Project |
| A look at COM+ and .NET |
|
| Creating a Singleton Service with Visual Studio .NET |
| MSDN |
| A common design pattern that I've seen used is the creation of a COM singleton that resides in a service. A service is a long-running executable that does not support a user interface, and which might not run under the logged-on user account. The service can run without any user being logged on to the computer. This makes services ideal for use on a server or whenever you need functionality that does not interfere with other users who are working on the same computer. |
|
| Distributing Objects in Visual Basic .NET |
| MSDN |
| The challenge we have faced in the past is that it isn't always easy to give a developer an object, especially across the network. Objects in COM are always passed by reference, meaning that the COM object remains in the process and on the machine where it was created. The client code merely gets a reference to the object, so each method call is marshaled across the network, back to the original object to be serviced. With Microsoft .NET, we have the option of passing our objects either by reference like COM, or by value. When an object is passed by value, we not only get a copy of the data, but we get an actual instance of the object on our client workstation. The object itself physically moves from the server machine to our client machine, meaning that our client application not only has the data we need, but we have the business logic relating to that data as well. |
|
| 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. |
|
| HOW TO: Create a remote server by using Visual C++ .NET |
| http://www.kbalertz.com/ |
| (818780) - This step-by-step article describes how to create a simple, remote server that another application can access. The application that accesses the server can be located on the same computer, on a different computer, or on a different network. The remote... |
|
| HOW TO: Create a Remote Server Using Microsoft Visual C# .NET (Q307445) |
| http://www.kbalertz.com/ |
| This article illustrates how to create a simple, remote server that another application can access. The application that accesses this server can be located on the same computer, on a different computer, or on a different network. The remot |
|
| HOW TO: Create a Remote Server Using Microsoft Visual C# .NET (Q307445) |
| Microsoft Support |
| This article illustrates how to create a simple, remote server that another application can access. The application that accesses this server can be located on the same computer, on a different computer, or on a different network. The remot |
|
| HOW TO: Create client access to a remote server by using Visual C++ .NET |
| http://www.kbalertz.com/ |
| (818781) - This step-by-step article describes how to create a client that accesses a remote server. This client can be located on the same computer, on a different computer, or on a different network. This article builds on the following Microsoft Knowledge... |
|
| 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. |
|
| Microsoft .NET Remoting: A Technical Overview |
| MSDN |
| Microsoft® .NET remoting provides a framework that allows objects to interact with one another across application domains. The framework provides a number of services, including activation and lifetime support, as well as communication channels responsible for transporting messages to and from remote applications. Formatters are used for encoding and decoding the messages before they are transported by the channel. |
|
| Publish And Subscribe |
| The Code Project |
| This tutorial will introduce the concepts of publishing and subscribing data over a network using the C# programming language and will hopefully provide not only an understanding of how publish and subscribe applications work but should provide the reader with the tools needed to develop a publish and subscribe style application of their own. |
|
| 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. |
|
| 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. |
|
| Using Web Services for Remoting over the Internet |
| The Code Project |
| This article describes a design and implementation (C#) of the Remoting over Internet using the Web Service as a gateway into the Remoting infrastructure. The Web Service Gateway (Custom Remoting Channel) allows to enhance the remoting channel over Internet and its chaining with another heterogeneous channel. Consuming a remote object over Internet is full transparently and it doesn't require any special implementation from the remoting via intranet. The Web Service Gateway enables to create a logical model of the connectivity between the different platforms and languages. Before than we will go to its implementation details, let's start it with usage and configuration issue. For some demonstration purpose I will use a MSMQ Custom Remoting Channel (MSMQChannelLib.dll), which I described in my previously article [1]. I am assuming that you have a knowledge of the .Net Remoting and Web Service. |
|
| 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. |
|
