Had to investigate some Assembly Loading issues, so I wrote two batch files to enable and disable the .NET Fusion Log:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| reg add "HKLM\Software\Microsoft\Fusion" /v EnableLog /t REG_DWORD /d 0 /f |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| reg add "HKLM\Software\Microsoft\Fusion" /v EnableLog /t REG_DWORD /d 1 /f |
They modify the HKLM\Software\Microsoft\Fusion key REG_DWORD value EnableLog.
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 1DWORD LogFailuresset value to 1DWORD LogResourceBindsset value to 1String LogPathset value to folder for logs e.g. C:\FusionLog\ (ensure the final backslash is there and the folder exists).
–jeroen
via:
- .NET enable and disable Fusion log.
- Answers to c# – How to enable assembly bind failure logging Fusion in .NET – Stack Overflow:
- Answer by user32736.
- Answer byMike Goatly.
- Answer by Gary Kindel.
The Wiert Corner - irregular stream of stuff 