Saturday, March 26, 2016

Enable logging of .Net assembly binding via registry

You have a .Net application that fails to load and you are suspecting that it may have to do with assembly dependencies. On a development machine fuslogvw.exe will aid you in collecting failed assembly binding but fuslogvw.exe is not normally available on production environment. So what do you do?

Logging of assembly binding can be enabled via the Registry, to do so navigate to HKLM\Software\Microsoft\Fusion. Add the following keys with corresponding values:

Key
Type
Value
ForceLog
DWORD
1
LogFailures
DWORD
1
LogResourceBinds
DWORD
1
LogPath
String
C:\FusionLog\









You need to restart the .Net application under test for this to take effect. The log files will be saved in C:\FusionLog.

Reference(s):
http://stackoverflow.com/questions/1012252/using-fuslogvw-exe-on-a-machine-with-no-visual-studio-installed


No comments: