Why do you need the fullblown assembly? Can't you just share interfaces? I guess I don't understand enough about the need here.
Using interfaces that describe the objects, you can distribute a common library. That's a major aspect of the concept of services -- web, remoting, WCF. You have shared interfaces defining operations and objects. ∞ 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 Wed, Oct 14, 2009 at 9:59 AM, Pat <[email protected]> wrote: > > Andy, > > Thanks for writing. I believe you, but I'm still stuck, then. > > As described above, I need a way to have compiled DLLs on one machine > able to run on another, and the client program on the machine running > them will never know which ones they are. They will all be run from a > single client that I have written, though. > > What are the better ways to accomplish this, if not the way I > described here: > http://www.vbdotnetheaven.com/UploadFile/rahul4_saxena/Reflection09122007031247AM/Reflection.aspx > ? > > TIA! > > :) > > On Oct 13, 3:39 am, Andrew Badera <[email protected]> wrote: >> What you're talking about doing is potentially extremely dangerous! >> Elevation city! Even if it's internal, you're not just opening a door >> you don't want to open -- you're CREATING a door that shouldn't be >> there. >
