On Wed, Apr 30, 2008 at 8:36 PM, M. David Peterson <[EMAIL PROTECTED]> wrote:
> On Wed, 30 Apr 2008 21:14:23 -0600, Curt Hagenlocher <[EMAIL PROTECTED]> > wrote: > > One advantage of having "one dll per library" is that you can make > > decisions about which DLL to load based solely on the library name. Once > > you have multiple libraries per DLL, you need a more complicated probing or > > mapping scheme to know which assembly to load. > > > > Why not meet half way: Generate netmodules who's primary purpose, if I am > remembering correctly, is the ability to be merged together into a final > assembly. This isn't dynamic, though. There has to be a single manifest for the assembly that lists all the netmodules. I imagine it would be desirable to be able to add a new library simply by copying it into the appropriate directory without having to register it or relink the assembly. -- Curt Hagenlocher [EMAIL PROTECTED]
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
