我现在正在与AssenblyResolve事件挣扎一段时间。我搜索了stackoverflow并做了其他谷歌搜索,并尝试了所有我认为相关的。以下链接更接近我的问题(在我看来):
AssemblyResolve is not invoked and FileNotFoundException is thrown during serialization
我有一个带有静态方法的Bootstrapper类(为了清楚起见,我将删除我们拥有的线程安全代码:
public static void Initialize()
{
AppDomain.CurrentDomain.AssemblyResolve += CustomResolve;
}
private static Assembly CustomResolve(object sender, ResolveEventArgs args)
{
// There is a lot code here but basicall what it does.
// Is determining which architecture the computer is running on and
// extract the correct embedded dll (x86 or x64). The code was based
// on milang on GitHub (https://github.com/milang/P4.net). And it's the same
// purpose we want to be able to load the x86 or x64 version of the perforce dll
// but this time with the officially Perforce supported p4api.net.
// Once the dll is extracted we assign it to the boostrapper
Bootstrapper._p4dnAssembly = Assembly.LoadFile(targetFileName);
// Make sure we can satisfy the requested reference with the embedded assembly (now extracted).
AssemblyName reference = new AssemblyName(args.Name);
if (AssemblyName.ReferenceMatchesDefinition(reference, Bootstrapper._p4dnAssembly.GetName()))
{
return Bootstrapper._p4dnAssembly;
}
}
如果我有一个带有main方法和静态构造函数的简单类,我能够使代码工作。静态构造函数只是调用Boostrapper.Initialize()方法。 在那之后,我可以使用我的库,它按预期工作:
public static class Test
{
static Test()
{
Bootstrapper.Initialize();
}
public static void Main()
{
// Using the library here is working fine. The AssemblyResolve event was
// fired (confirmed by a breakpoint in Visual Studio)
}
}
我遇到的问题是,是否存在至少一层依赖关系。基本上代码保持不变,但这次我的库代码在另一个库中:
public static class Test
{
static Test()
{
Bootstrapper.Initialize();
}
public static void Main()
{
Class1 myClass = new Class1();
// The following line is using the code of the extracted library, but
// The AssemblyResolve event is not fired (or fired before I register the
// callback) and therefore the library is not found : result
// BadImageFormatException() error could not load libary because one
myClass.Connect();
}
}
听起来像我之前说过的链接中的#2解释了我所看到的但是它不起作用。永远不会遇到AssemblyResove回调上的Visual Studio断点。
知道发生了什么事吗?
弗朗西斯
答案 0 :(得分:23)
我知道已经有一段时间了,因为这个问题被问到并得到了回答,但是我还想加上我对这个问题的看法(因为我浪费了几个小时的时间,也许多亏了别人不会#39; t必须)
问题基本上是这样的事实:应用程序正在尝试解析在该方法开始时执行该方法所需的所有程序集:
static void main(string[] args)
{
// <-- here the app tries to resolve MyAssembly
// and as MyAssembly.Class1 is not found, the app crashes
// this next line is never called:
AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(ResolveAssembly);
// class contained in an assemnly that we need to resolve
MyAssembly.Class1 myClass = new MyAssembly.Class1();
}
这就是为什么上面会崩溃:ResolveAssembly事件处理程序将永远不会被调用,因为它从未被连接过。
这也是以下解决方案有效的原因(由OP发布):
static void main(string[] args)
{
Initialize();
RealMain();
}
static void Initialize()
{
AppDomain.CurrentDomain.AssemblyResolve += new ResolveEventHandler(ResolveAssembly);
}
static void RealMain()
{
// <-- here the app tries to resolve MyAssembly
// class contained in an assemnly that we need to resolve
MyAssembly.Class1 myClass = new MyAssembly.Class1();
// and everything is OK
}
答案 1 :(得分:8)
有人确实回答了,但答案已被删除。所以我无法将其标记为已回答。 基本上,代码不需要在“主要”方法之外的事实是有效的。 从一个新项目重新开始,解决问题所以我想我有一些dll的问题(可能是x64文件夹中的x86 dll,反之亦然)
static void main(string[] args)
{
Boostrapper.Initialize();
RealMain();
}
static void RealMain()
{
Class1 myClass = new Class1();
myClass.Connect();
}