ansaurus

Question

.NET: Load two version of the same DLL

Answer 1

+3 A:

Check out Activator.CreateInstance() on MSDN. Code samples within.

http://msdn.microsoft.com/en-us/library/ms224132.aspx

No Refunds No Returns 2010-01-06 23:00:45

Answer 2

+2 A:

Here is a guide to do that

extern alias oldVer;
extern alias newVer;

and when compile:

csc /r:oldVer=Somepath\ClassLibrary.dll /r:newVer=AnotherPath\ClassLibrary.dll program.cs

or in visual studio change the "aliases" field in the property tab of your proyect references alt text

Kristian Damian 2010-01-06 23:01:20

We had some problem with this approach if ClassLibrary.dll references another assembly, the clr would only resolve the first version of the dependency, the second version dependency was resolved as the first version. We had to subscribe to AppDomain.ResolveAssembly and do some nasty things to overcome this problem.

SelflessCoder 2010-01-06 23:09:13

My test harness is already written in VB, so of course that would have to be a C#-only feature.

Jonathan Allen 2010-01-07 03:48:01

Answer 3

+1 A:

Ok, it was actually a lot easier than I imagined.

    m_Assembly1 = Reflection.Assembly.LoadFile(IO.Path.Combine(System.Environment.CurrentDirectory, "Old Version\Some.dll"))
    m_Assembly2 = Reflection.Assembly.LoadFile(IO.Path.Combine(System.Environment.CurrentDirectory, "New Version\Some.dll"))

    Console.WriteLine("Old Version: " & m_Assembly1.GetName.Version.ToString)
    Console.WriteLine("New Version: " & m_Assembly2.GetName.Version.ToString)

    m_OldObject = m_Assembly1.CreateInstance("FullClassName")
    m_NewObject = m_Assembly2.CreateInstance("FullClassName")

From here on out I used late binding and/or reflection to run my tests.

Jonathan Allen 2010-01-07 20:35:23

ansaurus

tags:

views:

answers:

.NET: Load two version of the same DLL

related questions