wolfie78uk
Programmer
Hi,
When using .NET remoting, it is my understanding that (because the client requires type information about the remote object) a copy of the assembly containing the remote object must be present on the client machine.
Is this the case? If so, surely it defeats the object of using remote objects as I would need to have a local copy that was always kept in sync with the remote version.
I would like to store a repository of remote objects in a centralized location that my various 'client' aplications can retrieve objects from on an ad-hoc basis. This would involve some form of late binding because the type information would not be known until runtime.
Any comments would be appreciated.
Thanks,
Simon
When using .NET remoting, it is my understanding that (because the client requires type information about the remote object) a copy of the assembly containing the remote object must be present on the client machine.
Is this the case? If so, surely it defeats the object of using remote objects as I would need to have a local copy that was always kept in sync with the remote version.
I would like to store a repository of remote objects in a centralized location that my various 'client' aplications can retrieve objects from on an ad-hoc basis. This would involve some form of late binding because the type information would not be known until runtime.
Any comments would be appreciated.
Thanks,
Simon
