Phil Jones
8/8/2004 2:19:00 AM
Cheers Sunny. One solution I'm looking at here is to use COM+ (Enterprise
Services) and loosley coupled events. I'm reluctant however, as this makes
the app installation a bit more of a hassle.
--
===
Phil
(Auckland | Aotearoa)
"Sunny" <sunny@newsgroups.nospam> wrote in message
news:emr0CUveEHA.592@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> In article <#9RBBKseEHA.1604@TK2MSFTNGP11.phx.gbl>,
> phil_newsgroup@hotmail.com says...
> > I'm finding a situation where I have a Remoting object on a client
retrieved
> > from a server. The object appears to work fine - I can call methods on
it
> > successfully.
> >
> > BUT, when I attempt to add a handler to one of the remote object's
events I
> > get a [SerializationException] which says it cannot find the assembly
> > (containing the event handler).
> >
> > I'm not sure what's going on here. Is this error occuring from within
(A)
> > the remote assembly, or (B) within the assembly that is wiring up the
event.
> > Should I be able to connect to events of a remote object without the
remote
> > assembly knowing about the attaching assembly?
> >
> > Thanks everyone - this is really perplexing me!
> >
> > -
> > ===
> > Phil
> > (Auckland | Aotearoa)
> >
> >
> >
>
> Every class in .Net is identified by its namespace, name, and assembly
> in which is implemented. To use any class in remoting, you need access
> to the implementation at both sides.
>
> Sunny