[Mono-devel-list] Assembly referencing on Windows - Mono Tricks?

Tom Larsen tomar at apricot.com
Mon Sep 20 14:22:57 EDT 2004

Remember one of the features of the .Net Framework is "side by side 
assemblies".  You can have two "Something.dll" both in the gac that have 
different strong names.  The framework will service assemblies that can 
run against either.

Do you have a more concrete example?  Using "monodis" or "ildasm" should 
show you what the assembly is referencing and theoretically it should 
indicate different assemblies even though they are implemented by two 
different vendors (MS and Mono).  Of course I say this at work without 
compiling an example to double check. :-)

Tom Larsen

On Mon, 20 Sep 2004, Aaron Clauson wrote:

> Hi,
> I have been trying to figure out which assemblies are
> getting used when I compile with csc and msc and then
> execute with mono or the MS clr, all on Windows.
> I thought a good way would be to look at the strong
> name of the loaded assemblies but it appears mono is
> mirroring the .Net GAC, if not in exact contents at
> least in assembly names, and is using not only the
> same names and versions but also the same public key?
> This would make sense in order to allow apps compiled
> against .Net to run against mono without recompiling.
> However, doesn't this raise a security concern since
> the mono assemblies can't be signed with the private
> key (since it belongs to MS) and are therefore loading
> strong named assemblies that are falsely signed? Or am
> I just way off track?
> Aaron
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list