Actually the concept isn't entirely uncommon: check out dependency injection, and Microsoft's Unity framework.
You don't want to push entire assemblies around, but you may want to inject behavior or state on a class-by-class basis. However, if dependency injection doesn't solve the issue, C is right -- you shouldn't be pushing assemblies around. That's just not good design. Use solid SOA principles. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Oct 8, 2009 at 2:23 AM, Cerebrus <[email protected]> wrote: > > What I fail to understand is why you would transfer an assembly to the > client rather than usable data. > >
