Why doesn't fusion log binding errors?

Michiel van Oosterhout picture Michiel van Oosterhout · Oct 9, 2009 · Viewed 7.8k times · Source

I have added the following to the registry key Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion:

  • EnableLog DWORD 1
  • LogFailures DWORD 1

If I start an ASP.NET web site from Visual Studio it throws a Parser Error:

Could not load file or assembly 'CMS.Controls, Version=4.1.3518.21577, Culture=neutral, PublicKeyToken=834b12a258f213f9' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Now if I refresh or restart the Assembly Binding Log Viewer it's empty. Shouldn't it log this error?

Only when I add DWORD ForceLog 1 to the registry it logs the error. But then the log fills up with all the successful bindings as well, and since it doesn't sort by name, it's difficult to find the error in the list.

Thanks!

Answer

Norman H picture Norman H · Jul 8, 2010

This question is similar to How to enable assembly bind failure logging (Fusion) in .NET related to Fusion bind logging