Had to investigate some Assembly Loading issues, so I wrote two batch files to enable and disable the .NET Fusion Log:
reg add "HKLM\Software\Microsoft\Fusion" /v EnableLog /t REG_DWORD /d 0 /f
reg add "HKLM\Software\Microsoft\Fusion" /v EnableLog /t REG_DWORD /d 1 /f
They modify the
A few notes:
- It is very important to turn of the Fusion log settings as soon as you are finished investigating. Fusion logs potentially take a lot of resources.
- When you have a .NET host like ISS, you have to restart that host (for instance by running iisreset)
- There is also Fuslogvw.exe Assembly Binding Log Viewer, but I like logging over viewing as logs are persistent.
- There are more values under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusionyou can configure; see the answer by Gary Kindel on StackOverflow:
DWORD ForceLogset value to 1
DWORD LogFailuresset value to 1
DWORD LogResourceBindsset value to 1
String LogPathset value to folder for logs e.g. C:\FusionLog\ (ensure the final backslash is there and the folder exists).
|Reference:||dot NET enable and disable Fusion log to investigate assembly loading issues from our NCG partner Jeroen Pluimers at the The Wiert Corner blog.|