[Mono-bugs] [Bug 388425] Mono loads assembly from bin/ referenced in web. config regardless of its version number

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=388425

User robertj at gmx.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=388425#c1


Robert Jordan <robertj at gmx.net> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
                 CC|                                                |robertj at gmx.net
         AssignedTo|mono-bugs at lists.ximian.com                      |mhabersack at novell.com
          Component|misc                                            |Sys.Web
            Product|Mono: Runtime                                   |Mono: Class Libraries




--- Comment #1 from Robert Jordan <robertj at gmx.net>  2008-05-08 16:16:41 MST ---
-> Sys.Web

Marek, I did not debug this deeply, but it seems to be 
AssemblyPathResolver.GetAssemblyPath(): it has a "fall through" from
Assembly.Load to Assembly.LoadWithPartialName. I think it should not
fall back if the assembly name contains ",".

However, the real bug could be in mono's LoadWithPartialName: it does not
pay attention to bogus assembly names:

using System;
using System.Reflection;

class Test
{
        static void Main ()
        {
                // random version & public key:
                Console.WriteLine (Assembly.LoadWithPartialName ("MySql.Data,
Version=0.1.1.0, Culture=neutral, PublicKeyToken=f5687fc88969c44d"));
        }
}

On MS.NET, it returns null. On Mono, MySql.Data.dll from the current
directory is loaded.

Note that if an arbitrary MySql.Data is installed in the GAC, both
MS and Mono will return the GAC assembly if the assembly name passed to
LoadWithPartialName did not match an assembly exactly.

No wonder that LoadWithPartialName is deprecated ;-)


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.