How to enable assembly binding logging using the Fusion Log Viewer

Today I had an issue with a Visual Studio 2010 ASP.Net solution. The error I was getting was:

Could not load file or assembly 'ClientDependency.Core' or one of its dependencies. Access is denied.


Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.


Exception Details: System.IO.FileLoadException: Could not load file or assembly 'ClientDependency.Core' or one of its dependencies. Access is denied.
Source Error:


An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 


Assembly Load Trace: The following information can be helpful to determine why the assembly 'ClientDependency.Core' could not be loaded.


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


Well no matter what I did here it just wouldn't work, let alone what a confusing Registry path.
I searched around and noticed others just as confused as I was.

I eventually found the Fusion Log Viewer (x64) @ the following location "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\x64\FUSLOGVW.exe" Once you execute the Fusion Log Viewer, click on settings. This is set to "Log Disabled" by default.

Note: If the option buttons are disbled in the window, close the application, right click the Fusion Log Viewer, and Run As Administrator.
Once you turn on the logging, you can then either use the viewer or IE to see the error on the assembly binding.

Also, you may have to restart after changing the settings for logging.

Once you troubleshoot your error I would highly suggest turning logging back off, as it can be unnecessary overhead.