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. Again, if I remembering correctly, the original idea was that
you could have one team writing code in VB.NET and another in C#, and they
could both compile to netmodules which are then merged into a final
assembly via a post compilation merging process.
WARNING: My memory of the purpose of netmodules might be completely out of
whack.
--
/M:D
M. David Peterson
Co-Founder & Chief Architect, 3rd&Urban, LLC
Email: [EMAIL PROTECTED] | [EMAIL PROTECTED]
Mobile: (206) 999-0588
http://3rdandUrban.com | http://amp.fm |
http://www.oreillynet.com/pub/au/2354
_______________________________________________
Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core
