Building a Robust and Highly Scalable Distributed Architecture using VB.NET - How to Test Remoting Component Without Using Windows Service

(Page 5 of 6 )

The following are the steps which are to be followed very strictly (we are about to work with projects 1, 3, 4 and 5):

• This is continuation from previous section. None of the previous configuration should be changed to implement the remoting in a cool manner.
  
• Now move to MyTrail\ConsoleRemoteServer\bin folder using the same command prompt and execute ‘ConsoleRemoteServer.exe’, which should return a message ‘Press ENTER to stop this process’.  This makes remoting server ‘ON’. (Please see Fig 4)
  
  
  
  
  
• Leave it like that and open another Visual Studio Command prompt and move to MyTrail\ConsoleRemoteClient\bin folder and execute ‘ConsoleRemoteClient.exe’, which should return a message ‘Successful’. (Please see Fig 5)
  
  
  
  
  
• Check your table ‘tAreas’ where a dummy value ‘from Remoting Client (without WinService)’ gets inserted just to prove the Remoting functionality.
  
  
• Switch to ‘RemoteServer command prompt window’ and press ENTER to shut down the remoting server.

You can close one of the command prompt windows and keep the other to proceed through next section.

Let us further proceed to our final implementation i.e., executing a stored procedure using a COM+ serviced component as DAL, Remoting Component (hosted with Windows Service) as Business layer and a Console application as a Remoting Client.

Next: How to Test Remoting Component Using Windows Service >>
 

More Visual Basic.NET Articles
More By Jagadish Chaterjee

Comments On: Building a Robust and Highly Scalable Distributed Architecture using VB.NET

· I'm not seeing a fig 6.    · The image was found and placed in the article. We apologize for any inconveniences...    · Hello,Please in your article regarding the above message title, you did mention...    · The link is on the first page itself or...   >>> Post your comment now!