>
> Spam Catcher wrote:
>> "leotohill@gmail.com" <leotohill@gmail.com> wrote in
>> news:1161106543.520865.51380@i42g2000cwa.googlegroups.com:
>>
>> > In theory, the remoting client needs only the first assembly, so
>> > that .NET can build the proxy. If possible, I would like to avoid
>> > deploying the other assemblies on the client side.
>>
>> Only pass classes that are in a common layer that both the server and
>> client have access to.
>>
>> That way you won't use the wrong objects.
>
> What do you mean by "only pass classes" ?

TDC wrote:
> Create an assembly that defines just the functionality that you want to
> expose to the client. Do this with Interaces. (That should give you
> confidence that no code is running that you don't want). Then you just
> distrubute this definition assembly, and implement the interfaces on
> the server-side.
>
> Tom
>
>
>
> leotohill@gmail.com wrote:
> > My assembly has a remotable class, and dependencies on some other
> > application assemblies.
> >
> > In theory, the remoting client needs only the first assembly, so that
> > .NET can build the proxy. If possible, I would like to avoid deploying
> > the other assemblies on the client side.
> >
> > How can I be assured that .NET will not attempt to load those other
> > assemblies on the client side? I'm particularly concered about other
> > classes in that assembly that have static initializers that may call on
> > the dependent assemblies. Under what conditions will those static
> > intializers run?
> >
> > Thanks for any suggestions and advice.
> >
> > - Leo