Deploying Remote Object Assembly to Clients?

[Leon_Amirreza]

Hi,
Suppose in a scenario that security is not an issue; if I deploy a copy of
the Whole assembly that contains remote objects to clients which of the
following would happen?

1- The calls to methods are actually serviced and run in the client machine
(like when a sharing assembly is installed on GAC).
2- The calls are still forwarded to server despite the fact that the a copy
of the whole assembly exists on client machine.

[Marc Gravell]

Assuming it is configured for remoting, then 2.

Without the dlls (defining the object / interface model), I would
expect Fusion to throw a wobbly.

Marc

[Leon_Amirreza]

Considering the scenario mentioned:
Do I need to deploy the remote assembly (definig objects) only for
development of client App or does the client will need the assembly at
runtime too?

"Leon_Amirreza" <am**************@yahoo.comwrote in message
news:ur**************@TK2MSFTNGP05.phx.gbl...

Hi,
Suppose in a scenario that security is not an issue; if I deploy a copy of
the Whole assembly that contains remote objects to clients which of the
following would happen?

1- The calls to methods are actually serviced and run in the client
machine (like when a sharing assembly is installed on GAC).
2- The calls are still forwarded to server despite the fact that the a
copy of the whole assembly exists on client machine.

[Marc Gravell]

Here's a thought... try it! With either what you have at the moment,
or a simple "hello world", see what happens both with and without the
dll. I would /expect/ it to fail horribly without the dll at the
client... but my expectation is not always correct.

Marc