Assembly Binding Log Viewer (fuslogvw) not logging any bindings

Question

Assembly Binding Log Viewer (fuslogvw) is not logging bindings for any version of the framework installed on my machine.

I tried using a custom log location, the default log location, the default category, and the native images category.

Assembly Binding Log Viewer worked a few months ago. I'm on a 64-bit machine and am running C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\x64\FUSLOGVW.exe

Answer 1

Going into Internet Explorer --> Tools --> Internet Options --> Browsing History,Delete..., , checking Temporary Internet Files and clicking delete fixed my issue.

Thanks to this blog post: http://www.request-response.com/blog/CommentView,guid,9f383687-3e1e-4568-833b-ef80e0938337.aspx

Answer 2

After much frustration I have found that by default, fuslogw does not log assembly binding failures!

You need to click 'settings' then select "log bind failures to disk", otherwise you won't see anything in the window

Answer 3

If you're building an ASP.NET MVC application (or possibly any other application involving IIS) restarting IIS was required to start getting binding logs.

Answer 4

According to this post it uses the IE Cache for logging. So it is a better idea to avoid clearing the browsing history all together and click on Settings->Enable Custom Log Path and choose a directory where you won't be sharing with IE.

Answer 5

I use the script from this blog post to enable fuslogvw.exe's logging, without the need to use the exe itself.

The script can be downloaded here.

This script "enables" and "disables" custom settings for the Fusion Log Viewer tool.

Enabling settings will:

• Create a log folder (default: C:\fusionlogs)
• Add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\LogPath and set it to the log folder
• Set HKEY_LOCAL_MACHINE\SOFTWAR\Microsoft\Fusion\LogFailures to 1
• Optionally set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\ForceLog to 1
• Optionally set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\LogResourceBinds to 1

Disabling settings will:

• Delete the log folder and its contents
• Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\LogPath
• Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\LogFailures to 0
• Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\ForceLog to 0
• Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\LogResourceBinds to 0

Answer 6

The Assembly Binding Log Viewer (FUSLOGW.exe) has quite some glitches.

Like the fact that it does not bind errors by default when running or that you have to make sure to not add an additional backslash to a custom log path. You cannot use the UI to go on error hunt you literally have to scan the file system to read logs. Heck, you cannot even resize the app window.

There's so much wrong with it that I decided to write an alternative assembly binding log viewer named Fusion++ and put it on GitHub. It uses the same mechanics internally but parses the logs for you. You don't have to care for any settings at all, not even log paths 😉

You can get the latest release from here or via chocolatey (choco install fusionplusplus).