Prateek wrote:

> I am developing a remoting service which is accessed by a client
> application using remoting.

> 1 - Developed a dll called Remotable.dll which is a type deployed on
> server
> 2 - Developed a consol listener which host this remotable type and
> listen for the client required on the http channel and on port 8002
> 3 - Developed a consol client application which takes the URL of the
> server and try to run a method of the remotable type hosted on the
> server.
>
> Now at point 3, I am getting and error "Cannot load type <Type Name>
> <Assembly Name>"

Prateek wrote:
> In order to simplify, I have copied the Remotable.dll in the client as
> well such that client.exe and remotable.dll remains in the same
> directory.
>
> still its not wworking...
>
>
> Phill W. wrote:
>
>> Prateek wrote:
>>
>>> I am developing a remoting service which is accessed by a client
>>> application using remoting.
>>> 1 - Developed a dll called Remotable.dll which is a type deployed on
>>> server
>>> 2 - Developed a consol listener which host this remotable type and
>>> listen for the client required on the http channel and on port 8002
>>> 3 - Developed a consol client application which takes the URL of the
>>> server and try to run a method of the remotable type hosted on the
>>> server.
>>>
>>> Now at point 3, I am getting and error "Cannot load type <Type Name>
>>> <Assembly Name>"
>> In order to create the proxy (to access the Remoted object), the client
>> process has to "know" some things about the Remoted class. In my
>> installation, that means deploying a /copy/ of the Assembly that defines
>> the Remoted class to a directory from which the client process can
>> access (i.e. load) it.
>>
>>
>> There's another way involing the use of Interfaces but, AFAIK, it still
>> involves deploying something client-side.
>>
>> HTH,
>> Phill W.