Microsoft KB Archive/300943

= How To Create Client Access to Remote Server by Using Visual Basic .NET =

Article ID: 300943

Article Last Modified on 5/9/2007

-

APPLIES TO


 * Microsoft .NET Framework Class Libraries 1.0
 * Microsoft Visual Basic .NET 2002 Standard Edition

-



This article was previously published under Q300943



The following .NET Framework Class Library namespace is referenced in this article:

System.Runtime.Remoting



This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location from which you downloaded the release.

For a Microsoft Visual C# .NET version of this article, see 307739.



For a Microsoft Visual Basic 6.0 version of this article, see 266717.

IN THIS TASK
SUMMARY
 * Requirements
 * How to Create a Client to a Remote Server

REFERENCES



SUMMARY
This step-by-step procedure demonstrates 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:

300951 How To Create a Remote Server by Using Visual Basic .NET

back to the top

Requirements
The following list outlines the recommended hardware, software, network infrastructure, and service packs that you need:
 * Microsoft Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows NT 4.0 Server
 * Microsoft Visual Studio .NET

This article assumes that you are familiar with the following topics:
 * Visual Studio .NET
 * Networking

You must also build applications that are described in 300951 before you begin the procedure in this article.

back to the top

How to Create a Client to a Remote Server
 Create a new Console Application in Visual Basic .NET. Module1 is created by default. Rename the module from Module1.vb to ClientApp.vb. Add a reference to the System.Runtime.Remoting namespace to the project. Add a reference to the ServerClass.dll assembly that you created in 300951.

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).  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. 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.</li> 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.</li></ol> </li>  Use the Imports statement on the Remoting, Remoting.Channels, and Remoting.Channels.Tcp namespaces and the ServerClass class name so that you are not required to qualify declarations in those namespaces later in your code. You must use the Imports statement prior to any other declarations. Imports System.Runtime.Remoting Imports System.Runtime.Remoting.Channels Imports System.Runtime.Remoting.Channels.Tcp Imports ServerClass </li>  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 the main module: Dim chan As TcpChannel = New TcpChannel ChannelServices.RegisterChannel(chan) </li>  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 in the code: <ol style="list-style-type: lower-alpha;"> 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. Because you did not specify a namespace in the previous section, the default root namepace is used.</li> 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 .</li></ol>

Dim obj As myRemoteClass

Obj = CType(Activator.GetObject( _ Type.GetType(&quot;myRemoteClass, ServerClass&quot;), _ &quot;tcp://localhost:8085/RemoteTest&quot;), myRemoteClass)

If obj Is Nothing Then Console.WriteLine(&quot;Could not locate server&quot;) Else If obj.SetString(&quot;Sending String to Server&quot;) Then Console.WriteLine(&quot;Success: Check the other console to verify.&quot;) Else Console.WriteLine(&quot;Sending the test string has failed.&quot;) End If End If                   </li>  Use the ReadLine method of the Console object to keep the client application running. Console.WriteLine(&quot;Press <ENTER> to exit...&quot;) Console.ReadLine </li> Build your project.</li> Make sure that the server application is running. (This refers to the .exe file that you created in 300951.)</li> Run the project, and test the client-to-server communication.</li></ol>

back to the top