> Retry on this (sent the original messages from the wrong account)---
> PLEASE NOTE: Jb has already replied, his follow-up I will attach in a
> separate follow-up
> ---

> Original Post
> -------------------

> This sounds like exactly what Cecil was designed for.  I've Cc'd Jb Evain,
> Cecil's creator and a member of the Mono Project team.

> Jb: Please see Dr. Kelly's overview of the problem at hand below.  What do
> you think?  Is Cecil the way to go?

> Dr. Kelly: A PDF overview of Cecil can be found @ http://evain.net/conf/Cecil-MonoMeeting07.pdf.
> An overview of the latest release and links to the source and binaries @ http://evain.net/blog/articles/2007/10/05/mono-cecil-0-6

> On Dec 13, 2007 11:40 PM, Wayne Kelly <w.ke...@qut.edu.au> wrote:

> > Ruby programs (such as RubyGems) can load multiple source files with the
> > same base name (ifthey are in different directories).

> > Eg:
> >  require 'A\foo'
> >  require 'B\foo'

> > Each of these source files may have already been separately compiled
> > into an assembly.
> > So, directory A might contain an assembly, presumably named foo.dll, as
> > might directory B.

> > If these assembly files are named foo.dll, then presumably the
> > assemblies will be named "foo".

> > .NET doesn't allow two assemblies with the same name to be loaded in the
> > same app domain.

> > This seems to imply that we need to strongly name all of our generated
> > assemblies;
> > and that we will need to use a different (randomly generated) key for
> > signing each assembly.

> > Please tell me I'm wrong.

> > Can anyone think of an alternative?

> > Cheers, Wayne.

> --
> /M:D

> M. David Peterson
> Co-Founder & Chief Architect, 3rd&Urban, LLC
> Email: m.da...@3rdandUrban.com | m.da...@amp.fm
> Mobile: (206) 418-9027
> http://3rdandUrban.com | http://amp.fm |
> http://www.oreillynet.com/pub/au/2354