How can I enable Assembly binding logging?

Question

I'm getting, "Could not load file or assembly 'Bla' or one of its dependencies. An attempt was made to load a program with an incorrect format."

A portion of the detailed info says:

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

So, thinking this may give me some insight in why I'm getting the error above (maybe the next YSOD would contain more explicit information about exactly why it's failing), I navigated to that location in the registry, but there is no such key that I can see. What it does have is:

\Fusion 
    (Default)   value not set
    \GACChangeNotification
    \NativeImagesIndex
    \PublisherPolicy

What am I missing?

Answer 1

When I had the same problem I fixed it by deleting the existing key.snk in that project and adding a new key.

Answer 2

A good place to start your investigation into any failed binding is to use the "fuslogvw.exe" utility. This may give you the information you need related to the binding failure so that you don't have to go messing around with any registry values to turn binding logging on.

Fuslogvw MSDN page

The utility should be in your Microsoft SDKs folder, which would be something like this, depending on your operating system: "C:\Program Files (x86)\Microsoft SDKs\Windows\v{SDK version}A\Bin\FUSLOGVW.exe"

1) Run this utility (it has a GUI) and set the settings to "Log bind failures to disk".

2) Click "Delete all" to clear the list of any previous bind failures

3) Reproduce the binding failure in your application

4) In the utility, click Refresh. You should then see the bind failure logged in the list.

5) You can view information about the bind failure by selecting it in the list and clicking "View Log"

The first thing I look for is the path in which the application is looking for the assembly. You should also make sure the version number of the assembly in question is what you expect.