当使用另一个屏幕中的测试结果视图运行调试测试时，Visual Studio 崩溃
当我尝试仅在调试模式下在“Microsoft Visual Studio Team System 2008 SP1”上运行单元测试并且“测试结果”视图在主屏幕以外的屏幕中打开（我有 2 个监视器）时，devenv.exe 进程崩溃。 您遇到过类似的错误吗？ 您找到解决方法了吗？
When I try to run unit tests, in debug mode only, on "Microsoft Visual Studio Team System 2008 SP1" and the Test Results view is open in a screen other than the main one (I have 2 monitors), the devenv.exe process crashes. Have you ever encountered a similar error? Have you found a workaround for it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我以前没有听说过这个问题。 如果您可以通过 Visual Studio Connect 就该问题提交错误，那就太好了。
客户错误，尤其是容易重现的错误，我们非常重视认真对待，并将予以考虑。
另外您介意在评论中发回 bug 的 ID 吗？
I have not heard of that issue before. It would be great if you could file a bug with Visual Studio Connect on the issue.
Customer bugs, especially easily reproducible ones, are taken very seriously and it will be looked at.
Also would you mind posting back in the comments what the ID of the bug is?
解决了我的场景：这是一个参考问题。 完全打开 Fusion 程序集绑定日志记录后，我发现（最近再次从 x86 移动到 x64）我在 web.config 中引用的库在为 x86 编译时是强命名的，但当我为任何 CPU 重新编译它们时或 x64，我没有使用强命名，因此有一个 null PublicKeyToken。 因此，框架在运行时不会通过名称找到实际上已部署的程序集。
错误的引用/程序集绑定问题/配置文件问题似乎是 .NET 的一个真正的症结所在——在很少或没有直接反馈的情况下，很可能会崩溃和烧毁，事件日志中几乎没有或没有任何有用的结果。
Resolved for my scenario: it was a reference issue. With Fusion assembly bind logging fully turned on, I found (having recently moved, again, from x86 to x64) that libraries I was referencing in a web.config were strong-named when compiled for x86, but when I recompiled them for Any CPU or x64, I hadn't used strong naming and therefore had a null PublicKeyToken. So assemblies that were in fact deployed, weren't being found by name by the framework at runtime.
Bad references/assembly bind issues/config file issues seem to be a real sticking point around .NET -- lots of potential for crashing and burning with little or no direct feedback, little or nothing useful ending up in the Event Log.