在 Blend 4 中设计时访问装配体
在 Blend 4 中设计时，我的代码出现异常。
我已将问题范围缩小到加载特定库。其他库可以正常加载，只有这个失败。因此，对于此代码：
var a = Assembly.Load("lib1");
var b = Assembly.Load("lib2");
第二行将引发异常：无法加载文件或程序集“lib2”或其依赖项之一。系统找不到指定的文件。
如果相同的代码在 Blend 之外运行，则不会抛出异常。这两个程序集在项目中的引用方式似乎相同，并且都标记为“复制本地”。
关于如何解决此问题有什么建议吗？
I am getting an exception from my code while designing in Blend 4.
I have narrowed the issue down to loading a specific library. Other libraries can be loaded fine, just this one fails. So, for this code:
var a = Assembly.Load("lib1");
var b = Assembly.Load("lib2");
Line two will throw an exception: Could not load file or assembly 'lib2' or one of its dependencies. The system cannot find the file specified.
If the same code is run outside of Blend, it does not throw. Both assemblies appear to be referenced the same way in the project, and both are marked Copy Local.
Any suggestions on how to troubleshoot this issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在设计时，Blend 会将程序集复制到输出文件夹之外的临时文件夹中，这样事情的表现就会与正常运行程序时不同。 Blend 还需要设计时的“任何 CPU”配置，因此如果您正常运行“x86”，您可能会得到不同的结果。
但 Blend 本身是一个像任何其他程序一样的托管程序，要详细诊断问题，您可以打开 Fusion Log Viewer 查看程序集绑定错误，以尝试找出问题所在。据推测，库本身就在它应该在的位置（在 Blend 的临时文件夹中），但未找到其间接依赖项之一。通过使用足够详细的日志查看器，您应该能够看到导致问题的特定绑定失败。
这是一个链接：
At design time Blend copies your assemblies to a temporary folder other than your output folder so things can behave differently than when you run the program normally. Blend also requires the "Any CPU" configuration for design time so if you run "x86" normally you can get different results simply because of that.
But Blend itself is a managed program like any other and to diagnose the problem in detail you can crack open the Fusion Log Viewer to see assembly binding errors to try to find out what is going wrong. Presumably the library itself is where it ought to be (in Blend's temporary folder) but one of its indirect dependencies is not being found. By using the log viewer with sufficient detail, you should be able to see the specific binding failure that is causing the problem.
Here is a link: