Library tutorials & articles
Using Interfaces In .NET Remoting
- Introduction
- Implementation & Server Object
- Creating the Client
- Conclusion
Creating the Client
To create the client program, go to File->New->Project and choose a C# Console Application named RemotingExampleClient.
IRemotingExampleService resService =(IRemotingExampleService)Activator.GetObject(
typeof(IRemotingExampleService),
"tcp://localhost:9988/RemotingExampleService");
Console.WriteLine("RESUME:\n"+ resService.GetFormattedResume());
Notice that we're using the IRemotingExampleService here instead of RemotingExampleService? That is because our client side code knows only about the interface, not the implementation the server is using. The result of this is the server is serving "RemotingExampleService", but our client is using "IRemotingExampleService".
IResume aResume = resService.GetResume();
Console.WriteLine("NAME:"+ aResume.GetFormattedName());
Console.WriteLine("RESUME:"+ aResume.GetFormattedResume());
This section of code makes use of the instance of IRemotingExampleService to return yet another interface. Here we don't have to make any calls to the Activator object because the .NET runtime accesses the server's Resume implementation transparently using the IResume interface.
To make this code work, we will need to add a referance to both our RemotingExampleInterfaces and System.Runtime.Remoting dlls as we did in step 2. Without this you will get compiler errors.
The complete code listing is below. For more information on the Activator object, see my article titled "Introduction to .NET Remoting" on this site.
using System;
using System.Runtime.Remoting;
using System.Runtime.Remoting.Channels.Tcp;
using System.Runtime.Remoting.Channels;
using RemotingExampleInterfaces;
namespace RemotingExampleClient
{
class RemotingExampleClient
{
static void Main(string[] args)
{
ChannelServices.RegisterChannel(new TcpClientChannel());
IRemotingExampleService resService =(IRemotingExampleService)Activator.GetObject(
typeof(IRemotingExampleService),
"tcp://localhost:9988/RemotingExampleService");
Console.WriteLine("RESUME:\n"+ resService.GetFormattedResume());
IResume aResume = resService.GetResume();
Console.WriteLine("NAME:"+ aResume.GetFormattedName());
Console.WriteLine("RESUME:"+ aResume.GetFormattedResume());
Console.WriteLine("Press any key to continue...");
Console.Read();
}//END OF MAIN METHOD
}//END OF RemotingExampleClient class
}//END OF RemotingExampleClient namespace
Compile this project and note the location of the .EXE file.
David Talbot is an experienced Software Architect with a diverse background including creating network applicances, working with
television set top boxes, building Billing/CRM systems, Web Portal...
Related articles
Related discussion
-
Are Native code making a comeback ? I think it never went away
by JoeGecko (0 replies)
-
Socket Programming in C# - Part 1
by graumanoz (23 replies)
-
Creating a Windows Service in VB.NET
by Templario55 (107 replies)
-
C# Windows Application Problem in Dynamically generated control
by BAmoozad (1 replies)
-
The Future of .NET Languages
by hack2root (2 replies)
Related podcasts
-
More jQuery in ASP.NET
In this episode Chris Brandsma, Rick Strahl, Dave Ward, Bertrand Le Roy, and Scott Koon conclude their discussion of Microsoft's jQuery in ASP.NET announcement1.This episode of the Alt.NET Podcast is brought to you by LLBLGen Pro, the most mature O/R mapper and code generator out there.Are ...
Events coming up
-
Nov
18
15 Minutes of Fame
Dresher, United States
This is a yearly tradition. We select 10 of the favorite speakers from monthly meetings, code camps, and hands on labs. Each one does a 15 minute talk on their favorite .NET technology. This is our 10th anniversary so we plan a gala event with special prizes and refreshments.
Hi,
I too have the same problem. Did you find any solution for that?
Regards
Paul
-----------------------------------VB Code------------------------------------------------------------
Sub Main()
ChannelServices.RegisterChannel(New HttpChannel())
Dim factory As RemotingClientsInterfaces.IAccountantExamFactory 'this is the object Im tring to remote
'this is the line where the excaption accure
factory = CType(Activator.GetObject( _
Type.GetType("RemotingClientsInterfaces.IAccountantExamFactory"), _
"http://10.0.0.172:8080/IExamFactory"), RemotingClientsInterfaces.IAccountantExamFactory)
.
.
.
---------------------------end of Code-------------------------------------------------------------------
See anything suspicious ???
Its time for me to be more specific.
I wrote a server client application in C# using remoting
and it worked. Then I replaced the client with another
clients written in VB.NET and got an exception while trying to create the remote object:
"An unhandled exception of
type 'System.ArgumentNullException' occurred in
mscorlib.dll
Additional information: Value cannot be null."
do you have any suggestions what so ever ???
My E-Mail: assaf@nipendo.com
Thanks
Unless a developer get the comparision between two technologies he/she may not choose the new one.
Ghanshyam.
Hi,
Can you please pass me the Client application source code for your article .Net Remoting. I think you forgot to upload in your site at http://www.developerfusion.com/show/2082/3/
Can you please forward the source code to my e-mail ID @ r_nazermd@yahoo.com
Thanks and Regards
Nazer Mohamed
Good article. The client side code was missing until I went to the printer friendly version. I ran the code and it worked as expected.
I have a couple of questions about interfaces. Is it possible to initialize a type "such as byte [] array" within the main program and allow the interfaces to access that initialized type so that the clients could do something with it? I thought that the use of interfaces would be a good tool for clients to use to get information from a server that is constantly polling external data. The only examples that I have seen so far, show me that the main thread is completely separate from the interfaces. Is this true?
Tom McDaniel
This thread is for discussions of Using Interfaces In .NET Remoting.