I\'m writing a .NET library to inject managed DLLs into external processes. My current approach is:
CreateRemoteThread
to force the target pro
Found the fix for this problem here: http://www.west-wind.com/WebLog/posts/601200.aspx
It looks like a bug in the .NET framework. The solution is to add a handler to AppDomain.CurrentDomain.AssemblyResolve
which manually loads & returns the assembly at args.Name
. Then you can call CreateInstanceFromAndUnwrap
without it throwing an exception.