How to create client access to remote server by using Visual C#

For a Microsoft Visual Basic .NET version of this article, see
300943 .

This article refers to the following Microsoft .NET Framework Class Library namespaces:
  • System.Runtime.Remoting
  • System.Runtime.Remoting.Channels
  • System.Runtime.Remoting.Channels.Tcp



This step-by-step article shows you 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 upon the following Microsoft Knowledge Base article:
307445 Create a Remote Server by Using Microsoft Visual C# .NET


This list outlines the recommended hardware, software, network infrastructure, and service packs that you will need:

  • Microsoft Visual Studio .NET or Microsoft Visual Studio 2005
This article assumes that you are familiar with the following topics:
  • Visual Studio .NET or Visual Studio 2005
  • Networking
You must also build applications that are described in
307445 before you begin the procedure in this article.

How to Create a Client to a Remote Server

  1. Create a new Console Application in Visual C# .NET or in Visual C# 2005. Class1 is created by default.

    Note In Visual C# 2005, Program.cs is created by default.
  2. Rename Class1.cs to ClientApp.cs.
  3. Add a reference to the System.Runtime.Remoting namespace to the project.
  4. Add a reference to the ServerClass.dll assembly that you created in
    307445 .

    There are three different ways for a client to reference remote objects, and each of these is resolved at compile time. This example uses the first option (a).
    1. Compile the server object, and specify the .exe or .dll file as a reference to the compiler when you compile the client. This method is useful when both the client and server components are developed at the same site.
    2. Derive the server object from an interface class, and compile the client with the interface. This method is useful when the client and server components are not developed at the same site. The interface(s) can be compiled to a dynamic-link library (DLL) and shipped to the client sites as necessary. As much as possible, avoid changing a published interface.
    3. Use the SoapSUDS tool to extract the required metadata from a running server object. This method is useful when client and server components are developed at different sites, and no interface classes are available. Point the SoapSUDS tool at a remote Uniform Resource Identifier (URI), and generate the required metadata as source or a DLL. It is important to note that the SoapSUDS tool only extracts metadata; it does not generate the source for the remote object.
  5. Use the using statement on the Remoting, Remoting.Channels, and Remoting.Channels.TCP namespaces and the ServerClass classname so that you are not required to qualify declarations in those namespaces later in your code. You must use the using statement prior to any other declarations.
    using System;
    using System.Runtime.Remoting;
    using System.Runtime.Remoting.Channels;
    using System.Runtime.Remoting.Channels.Tcp;
    using ServerClass;
  6. Declare a variable to initialize a TcpChannel object that the client will use to connect to the server application. Use the RegisterChannel method to register the channel with the channel services. Add the following declaration code in the Main procedure of Class1:
    TcpChannel chan = new TcpChannel();
  7. Declare and instantiate the remote server. In this example, use the GetObject method of the Activator object to instantiate the myRemoteClass object, and specify the following parameters:
    • The full type name of the object that is being registered (which is ServerClass.myRemoteClass in this example), followed by the assembly name ServerClass. Specify both the name of the namespace as well as the classname here. Because you did not specify a namespace in the previous section, the default root namepace is used.
    • Activate the URI of the object. The URI must include the protocol (TCP), the computer name (localhost), the port (8085), and the endpoint of the server object (RemoteTest). To access the ServerClass remote server that is located on the local server, use the URI "tcp://localhost:8085/RemoteTest".
      myRemoteClass obj = (myRemoteClass) Activator.GetObject(typeof(myRemoteClass),
      if (obj == null)
      System.Console.WriteLine("Could not locate server");
      if (obj.SetString("Sending String to Server"))
      System.Console.WriteLine("Success: Check the other console to verify.");
      System.Console.WriteLine("Sending the test string has failed.");
  8. Use the ReadLine method of the Console object to keep the client application running.
    System.Console.WriteLine("Hit <enter> to exit...");
  9. Build your project.
  10. Make sure that the server application is running. (This is the EXE file that you created in
    307445 .)
  11. Run the project, and test the client-to-server communication.


For an overview of .NET Remoting, see the Microsoft .NET Framework Developer's Guide.

For more information about the TcpChannel class, visit the following Microsoft Web site: For an introduction to the Microsoft .NET Remoting Framework (general .NET Development technical articles), visit the following Microsoft Web site:
An Introduction to Microsoft .NET Remoting Framework
For more information about .NET Remoting, visit the following Microsoft Web site:
Microsoft .NET Remoting: A Technical Overview
For more information about the Activator.GetObject and Type.GetType methods, see the .NET Framework Class Library documentation.

 For more information, refer to the following books:
Tom Archer Inside C# Microsoft Press, 2001
Charles Petzold Programming Microsoft Windows with C# Microsoft Press, 2001

Mickey Williams Microsoft Visual C# (Core Reference) Microsoft Press, 2002

ID articol: 307739 - Ultima examinare: 19 oct. 2012 - Revizie: 1