TestDriven.NET 下的测试未获取更新的 fuslogvw 设置
如果有重复的内容,我会投票给它,但直到有人为我找到它......这是我今天学到的东西[似乎没有人在博客上提到]条目......
使用 TestDriven.NET ,我不断从 Assembly.Load
获得以下输出:
警告:程序集绑定日志记录已关闭。
要启用程序集绑定失败日志记录,请将注册表值 >[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) 设置为 1。
注意:程序集绑定失败日志记录会带来一些性能损失。
要关闭此功能,请删除注册表值 [HKLM\Software\Microsoft\Fusion!EnableLog]。
所以我加载了fuslogvw,并且由于我在x64系统上,甚至尝试了相同的x64版本,但无论我重试多少次,都无法让它显示日志。我验证了注册表中的设置,一切看起来都应该如此 - EnableLog
已设置,但重新运行时仍然没有任何乐趣。
If there's a dup of this, I'll be upvoting it but until someone finds it for me.... This is a Things I've Learned Today [that nobody seems to have blogged about] entry...
With TestDriven.NET, I was continually getting the following output from an Assembly.Load
:
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value >[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
So I loaded fuslogvw, and as I'm on an x64 system, even tried the x64 version of same, but couldnt get it to display the log, no matter how many times I retried. I verified the settings in the registry, and everything seemed as it should be - EnableLog
was set, but still no joy on the re-run.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
事实证明,该设置的值会缓存在进程中,并且由于 TestDriven.net 会保留一个进程 (ProcessInspiration.exe) 以提供快速启动,因此如果不单击托盘图标(红色干草叉),它就不会拾取该进程)并选择“停止”[以在下次运行时触发重新加载]。所以现在,我得到:
...
正如所希望的...
Turns out that the value of the setting gets cached within the process, and as TestDriven.net keeps a process (ProcessInvocation.exe) hanging around to provide a quick startup, it doesnt pick it up without one clicking on the tray icon (red pitchfork) and selecting Stop [to trigger a reload on the next run]. So now, I get:
...
Just as desired...