[Mono-bugs] [Bug 366794] New: Assembly.LoadFrom() fails due to wrongly caring about < SpecificVersion>

[bugzilla_noreply at novell.com]

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


           Summary: Assembly.LoadFrom() fails due to wrongly caring about
                    <SpecificVersion>
           Product: Mono: Runtime
           Version: 1.2.4
          Platform: x86
        OS/Version: Ubuntu
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: shane at actionengine.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Development


I have a situation where mono is being too picky about an assembly version.

I have a Visual Studio 2005 solution with two C# projects:

   -  main.exe (a command-line app)
   -  api.dll (an assembly used by main.exe and others)

I have a second Visual Studio 2005 solution with one C# project:

   -  myapp.dll

The myapp.dll depends on and calls into api.dll, but NOT a specific version of
it.  In other words, myapp.dll's project contains this line when referencing
api.dll:

   -  <SpecificVersion>False</SpecificVersion>

So I compile my two solutions using Visual Studio 2005 and then move the
binaries over to ubuntu 7.10 to run them under mono 1.2.4.

When main.exe runs, it tries to load myapp.dll via Assembly.LoadFrom(...).  It
works fine as long as the exact same version of api.dll is used by main.exe and
myapp.dll.  But the load fails if the two versions of api.dll are different. 
Normally this is desirable of course, but not when the .csproj contains the
SpecificVersion = False instruction.

We have a mature product that relies on this type of API model, which has been
running fine for years in Windows/Microsoft .NET.


-- 
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.