Groups | Blog | Home
all groups > dotnet remoting > february 2007 >

dotnet remoting : Creating instance of remote server object



Cairn
2/17/2007 6:59:07 AM

I am attempting to create a client activated system. I have a interface dll
which contains the interface to be used, this assembly is then referanced in
both client and server. The server implemenation is then split in to a DLL
which contains the server code, and an app which creates and instance of the
server code. (This is so that I have a console app for debuging, and a
service app for final release).
My question, in the client when I call Activator.CreateInstance what name do
I used for the assemblyName. I have attempted differant names but all of them
rasied exceptions. I also noted looking in the newsgroup where it was
mentioned registering the bits within the GAC, is this required and how

Oliver Sturm
2/18/2007 6:51:44 PM
Hello Cairn,

[quoted text, click to view]

I'm not sure I understand this part of your question. On the client, you
would normally call Activator.GetObject(), not CreateInstance, and pass
the URL of the service, not a reference to any assembly. It would probably
help if you posted some sample code that shows what exactly you're doing.

[quoted text, click to view]

I guess it depends on your definition of "the bits". In any number of
Remoting scenarios, you don't have to register any of the application
assemblies in the GAC.


Oliver Sturm
--
AddThis Social Bookmark Button