Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 18 | Comments: 66

filter by tags archive

Solving the Assembly Load Context Problem

time to read 7 min | 1296 words

One of the more annoying things about the way .Net is handling assemblies is the load context. If you load an assembly using Assembly.LoadFile(), it will not be available if you then do Assembly.Load().
There are any number of scenarios where this is a major hurdle. Any kind of plug in architecture, for instance. After getting bit by this when I wrote NHibernate Query Analyzer, I know way too much about resolving assemblies and the problems that this entails.
It can get much worse when you try to load assemblies from locations that are not in your private bin path. Anyway, I put together a small class that will fix this issues for me.

public static class AssemblyLocator

{

    static Dictionary<string, Assembly>assemblies;

   

    public static void Init()

    {

        assemblies = new Dictionary<string, Assembly>();

        AppDomain.CurrentDomain.AssemblyLoad += new AssemblyLoadEventHandler(CurrentDomain_AssemblyLoad);

        AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(CurrentDomain_AssemblyResolve);

    }

 

    static Assembly CurrentDomain_AssemblyResolve(object sender, ResolveEventArgs args)

    {

        Assembly assembly = null;

        assemblies.TryGetValue(args.Name, out assembly);

        return assembly;

    }

 

    static void CurrentDomain_AssemblyLoad(object sender, AssemblyLoadEventArgs args)

    {

        Assembly assembly = args.LoadedAssembly;

        assemblies[assembly.FullName] = assembly;

    }

}

As you can see, all you need to do is to call AssemblyLocator.Init(), and it will make sure that any assembly, not matter how it was loaded, will be accessible via Assembly.Load() and friends.


Comments

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. RavenDB 3.0 New Stable Release - one day from now
  2. Production postmortem: The industry at large - about one day from now
  3. The insidious cost of allocations - 3 days from now
  4. Buffer allocation strategies: A possible solution - 6 days from now
  5. Buffer allocation strategies: Explaining the solution - 7 days from now

And 3 more posts are pending...

There are posts all the way to Sep 11, 2015

RECENT SERIES

  1. Find the bug (5):
    20 Apr 2011 - Why do I get a Null Reference Exception?
  2. Production postmortem (10):
    01 Sep 2015 - The case of the lying configuration file
  3. What is new in RavenDB 3.5 (7):
    12 Aug 2015 - Monitoring support
  4. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
View all series

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats