Fusion Log Viewer 的替代品?
除了 Fuslogvw.exe 之外,是否还有其他 Fusion 日志查看器程序,或者将 Fusion 日志输出定向到您自己的目录,然后手动检查大量 HTM 文件?
我的两个主要抱怨是:
我想要一个概述,显示哪些程序集加载成功,哪些失败。
我不确定日志文件上时间戳的分辨率,因此我不确定哪个条目位于另一个条目之前。例如,我的程序显然正在尝试加载包含culture=da 和culture=da-dk 的程序集。它应该只是尝试加载 da-dk,事实上加载是成功的。那么为什么它也(不成功)尝试加载culture=da呢?如果我至少确定它尝试执行这些加载的顺序可能会有所帮助,但 Fuslogvw.exe 随机显示这两个条目,并且登录到私有目录也好不了多少。
Are there any alternative Fusion Log Viewer programs, other than Fuslogvw.exe, or directing the Fusion log output to your own directory and then examining the tons of HTM files by hand?
My two main gripes are:
I'd like an overview that showed which assembly loads succeeded and which failed.
I'm unsure of the resolution of the timestamps on the logging files, so I'm unsure of which entry comes before another entry. For example, my program is apparently trying to load an assembly with both culture=da and culture=da-dk. It should only be trying to load da-dk, and in fact that load is successful. So why is it also (unsuccessfully) trying to load culture=da? It might help if I at least was sure of the order in which it is trying to do these loads, but Fuslogvw.exe displays the two entries randomly, and logging to a private directory isn't much better.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
可能会迟到,但我认为 Fusion++ 非常适合您的问题。
它会带走您的一切 - 不再需要寻找文件:只需单击“记录”即可捕获程序集日志。如果完成,再次单击“停止”,Fusion++ 将为您解析所有日志文件。
Might be late to the party but I think Fusion++ is a pretty good match for your question.
It takes everything away from you - no more file hunting: Just click "Record" to capture assembly logs. If you are done, click "Stop" again and Fusion++ will parse all the log files for you.
Fusion Log Viewer 所做的只是翻转一些注册表设置并检查日志文件。
根据融合加载器的输出,可能无法准确确定每个程序集的加载时间。在这方面,聚变装载机有点像黑匣子。
最好的选择可能是使用调试器直接进入应用程序并观察 Visual Studio 中的“模块”窗口。如果您仔细地逐步浏览该应用程序,您应该能够看到每个程序集在哪个点加载到内存中。
All the Fusion Log Viewer does is flip some registry settings and examine the log files.
It might not be possible to determine exactly when each assembly is loaded based on the fusion loader's output. The fusion loader is somewhat of a black box in that respect.
Your best bet might be to step directly into your application with the debugger and watch the Modules window in Visual Studio. If you step carefully through the application, you should be able to see at which point each assembly gets loaded into memory.