Compiling and Running Remote Application

The .NET Remoting is one of several ways to establish communication between application domains using the .NET Framework.

The main three components of a Remoting Framework are a Remotable Object , Listener Application for listening requests for remote object and a Client Application makes requests for remote object. Additionally you need Configuration files for your Listener Application and Client Application.

Compiling the VB.Net source code files

Create a new folder SRC and put the three VB.Net source code files in that folder.

1. RemoteTime.vb

2. TimeListener.vb

3. Client.vb

Add the two configuration files in the same folder.

1. TimeListener.exe.config

2. Client.exe.config

Compile these VB.Net class files using the command-line tools that ship with the .NET Framework SDK.

  1. vbc /t:library RemoteTime.vb
  2. vbc /r:RemoteTime.dll TimeListener.vb
  3. vbc /r:RemoteTime.dll Client.vb
Note: You have to provide the physical path of each source files when you compile the source code , for example : if the source code files are in the folder c:\SRC , you have to give path like:

After you complied the VB.Net source code files, you will get additional three files in the SRC folder. They are :

  1. RemoteTime.dll
  2. TimeListener.exe
  3. Client.exe

To run the application

Create two new folders and give the name like Server and Client respectively.

Copy RemoteTime.dll , TimeListener.exe and TimeListener.exe.config to the Server folder.

Copy RemoteTime.dll , Client.exe and Client.exe.config to the Client folder.

Open a command prompt on Server folder and type TimeListener

Then you will get a screen showing "Listening for requests from the Client. Press Enter to exit..."

Open a command prompt on Client folder and type Client.

Then you will get the current time from remote Object.

Now you have done your first .Net Remoting VB.Net project successfully . Try to explore more on Remoting ...
 (C) 2021    Founded by raps mk
All Rights Reserved. All other trademarks are property of their respective owners.
SiteMap  | Terms  | About