.Net Remoting

[shaziya]

Hi there,

I have created a remotig obj(dll) derived from MarshalByRefObject. I
have server application, client application.

If all these server exe, client exe and remorting dll are present in
same directory, and then if I run server exe, then client exe, it
works well.

But If my server exe and remoting dll are present in other directory
say C:, and my client exe is present at another exe say D: then it
doesn't work.

So my Question in these scenario Remoting concept is not getting
applied. And remoting means we can evev have distributed types of
application. But forget about distributed kind of application , it is
not working on same PC's different directory.

So can anyone plz help me where I am doing wrong, and what exactly i am
supposed to do in order to avoid such kind of problems.

Waiting for quick, positive reply.

Thanking you....

 

[Mehdi]

I have created a remotig obj(dll) derived from MarshalByRefObject. I
have server application, client application. [...]
But If my server exe and remoting dll are present in other directory
say C:, and my client exe is present at another exe say D: then it
doesn't work.

So my Question in these scenario Remoting concept is not getting
applied. And remoting means we can evev have distributed types of
application. But forget about distributed kind of application , it is
not working on same PC's different directory.

So can anyone plz help me where I am doing wrong, and what exactly i am
supposed to do in order to avoid such kind of problems.

The client application must have access to the known layer too (what you
have called the remoting DLL). If the client doesn't have access to the
known layer, how do you expect it to know the type of the remote objects
exposed by the server? Typically, the known layer DLL, shared by both the
client and the server application, contain the interfaces of all the remote
objects exposed by the server (but not their implementation). The server
application implements these interfaces and exposes the objects via .NET
Remoting. The client application simply connects to these remote obects and
does not need to know anything about their implementation (but it needs to
know at least their interfaces so that it knowns what methods these objects
have).

 

[shaziya]

ok so it is similar to RPC and RMI in java.

I have created a remotig obj(dll) derived from MarshalByRefObject. I
have server application, client application. [...]
But If my server exe and remoting dll are present in other directory
say C:, and my client exe is present at another exe say D: then it
doesn't work.

So my Question in these scenario Remoting concept is not getting
applied. And remoting means we can evev have distributed types of
application. But forget about distributed kind of application , it is
not working on same PC's different directory.

So can anyone plz help me where I am doing wrong, and what exactly i am
supposed to do in order to avoid such kind of problems.

The client application must have access to the known layer too (what you
have called the remoting DLL). If the client doesn't have access to the
known layer, how do you expect it to know the type of the remote objects
exposed by the server? Typically, the known layer DLL, shared by both the
client and the server application, contain the interfaces of all the remote
objects exposed by the server (but not their implementation). The server
application implements these interfaces and exposes the objects via .NET
Remoting. The client application simply connects to these remote obects and
does not need to know anything about their implementation (but it needs to
know at least their interfaces so that it knowns what methods these objects
have).