Hello,

I'm testing remoting 2.0. I created a library, server and client project.
The client project instantiates a remote object a display it in a property
grid. Everything works fine excepted the property grid. I would like to know
if there was a "declarative" way (config file) or other to solve my issue?

Thanks a lot
Serge

[attached file: RemotingLab.zip]

Hi,

Honestly, this is quite an inefficient design. Any remotable interfaces
should not be "chatty" (that is, the number of roundtrips between the client
and the server should be minimal). However, this is not the case with
PropertyGrid, who is known for querying the objects whose properties it
displays every now and then. Hence, what I'd recommend is creating a
dedicated "property bag" object which would be populated once by reading the
remote object's property values and then fed to the PropertyGrid to be
displayed. A sort of local cache of the remote data, plus you can implement
ICustomTypeDescriptor on this "property bag" to customize the appearance of
the property values.

Show quoteHide quote

About IDisposable.Dispose()
Delegate problem
Proper unmanaged to managed exception handling -- SEHException and
Implement a Time-out in the waitQueue of the ThreadPool
Class Library