>I have a simple MarshalByRefObject derived Object (remotableObject) in
> a separate assembly that is referenced by both remoting server and
> client. Both server and client contain a member of that type.
> RemotableObject also contains an event. This event can be fired by the
> server AND the client. When the server fires that event the client
> should get notfied, when the server fires that event the client should
> get notfied. Unfortunately the the latter does not happen. Whenever the
> remoting server fires the event the client's eventhandler method never
> gets called. (Both client and server added an eventhandler-method for
> remotableObject.SomeEvent). What am I doing wrong or what do I need to
> do to achieve the desired effect?
>
> On ther server side I marshal that meber like this:
>
> channel = new TcpChannel(8080);
> ...
> ChannelServices.RegisterChannel(channel,false);
> RemotingServices.Marshal(remotableObject, "MyUri",
> typeof(RemotableObject));
>
> On the client side I activate like this:
>
> channel = new TcpChannel();
> ChannelServices.RegisterChannel(channel, false);
> remotableObject = (RemotableObject)
> Activator.GetObject(typeof(RemotableObject),
> "tcp://localhost:8080/MyUri", null);
>

> I think you're in the same situation as I am with the thread "Client
> call backs".
>
> I've come to the conclusion that the problem is that an open
> connection is not established between the server and the client. All
> samples I found about client call backs generates the call backs in
> methods called by the client thus having an open connection.

"Spam Catcher" wrote:

> "Benny S. Tordrup" <nospam.bt.nospam@fk-data.nospam.dk> wrote in
> news:u5EgMbqmGHA.1552@TK2MSFTNGP04.phx.gbl:
>
> > I think you're in the same situation as I am with the thread "Client
> > call backs".
> >
> > I've come to the conclusion that the problem is that an open
> > connection is not established between the server and the client. All
> > samples I found about client call backs generates the call backs in
> > methods called by the client thus having an open connection.
>
> Yes, you need bidirectional remoting for this to work. Best thing - do not
> use events.
>
> Rather have the server "push" events to a client by calling a function on
> the client.
>
> http://www.codeproject.com/csharp/RemotingAndEvents.asp
>
> Sample #2 works well.
>