替代融合日志查看器？ [英] Alternative to Fusion Log Viewer?

问题描述

有没有替代的融合日志查看器程序较Fuslogvw.exe等，或指挥融合日志输出到你自己的目录，然后检查的HTM文件万吨的手？

我的两个主要的抱怨是：

1. 我想这表明该组件加载成功，而失败的概述。

2. 我不确定在日志文件中的时间戳的分辨率，所以我不能确定哪一个条目来另一个条目之前的。例如，我的程序显然是试图加载程序集既文化= DA和文化= DA-DK。它应该只试图加载哒-dk的，而事实上该负载是成功的。那么，为什么还（失败）试图加载的文化=哒？它可能会帮助，如果我至少可以肯定的，它是试图做这些负载的顺序，但Fuslogvw.exe显示两个条目随机，并记录到私有目录也好不到哪里去。

解决方案

所有的融合日志查看器的作用是翻转某些注册表设置和检查日志文件。

  HKEY_LOCAL_MACHINE \ SOFTWARE \微软\融合
加：
DWORD ForceLog设定值设置为1
DWORD LogFailures设定值设置为1
DWORD LogResourceBinds设定值设置为1
字符串日志路径设置值到文件夹的日志（例如C：\ FusionLog \）
 

有可能无法准确地确定当每一个组件是根据该融合加载器的输出加载。融合装载机是一个黑盒子在这方面有点。

您最好的选择可能是直接加强与调试应用程序，并观看在Visual Studio中的模块窗口。如果通过应用程序认真步骤，你应该能够看到在这一点每一个组件被加载到内存中。

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:

1. I'd like an overview that showed which assembly loads succeeded and which failed.

2. 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.

解决方案

All the Fusion Log Viewer does is flip some registry settings and examine the log files.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion
Add:
DWORD ForceLog set value to 1
DWORD LogFailures set value to 1
DWORD LogResourceBinds set value to 1
String LogPath set value to folder for logs (e.g. C:\FusionLog\)

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.

这篇关于替代融合日志查看器？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！