Assembly Binding Log Viewer (fuslogvw) not logging any bindings

Viewed 20400

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

6 Answers

The Assembly Binding Log Viewer (FUSLOGVW.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).

Fusion++

Related