Comments on: Run Anonymous Methods in Another AppDomain

By: mpb

mpb — Fri, 15 Oct 2010 09:04:58 +0000

Just in case someelse comes across the problem I encountered; figured it out…
Despite that the type to which we would like to unwrap is known in the default appdomain.. it can have trouble figuring this out at runtime apparently. You can resolve this by binding the AppDomain.CurrentDomain.AssemblyResolve event (ie. AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(SomeAssemblyResolve) obviously…)
the SomeAssemblyResolve will have an eventarg.Name.. this is the name of the assembly in question and can be loaded through System.Reflection.Assembly.Load(..) or Assemly.LoadFromPartialName(…) (although deprecated)..
When this event is handled… your proxy will be correctly unwrap towards the expected class.

Hope it helps someone

By: mpb

mpb — Wed, 13 Oct 2010 09:42:51 +0000

Hey matt,
I’ve been trying something very similar.. and hit a problem when hitting the createInstanceUnwrap() method. It creates
a transparentproxy without any problem, but it can’t be
casted to the type.
I tried your code to see what the difference would be..
turns out.. I get the same error?!
Did you come across this situation too?

regards,
Merijn

By: valerio.net » Blog Archive » Run Anonymous Methods in Another AppDomain, Part 2

Mon, 23 Jun 2008 02:43:17 +0000

[...] Run Anonymous Methods in Another AppDomain [...]