How to use Fusion Log to debug dll load issues in .net Application

When you get runtime errors, e.g. "Could not load file or assembly 'ZappySys.Json'", you can try enabling Fusion Logging (a .NET Framework feature) and then examine the logs. Perform the following steps: 

Step-1: Type "regedit" in search box. Open it
Step-2: Navigate to following reg key. On the Right side of \Fusion key ... Right click and add following Values
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion

Add:
 DWORD ForceLog (optional) - set value to 1  (This logs all dll binds - success and failed)
 DWORD LogFailures - set value to 1 (This logs only failed)
 String LogPath - set value to folder for logs (e.g. C:\FusionLog\)

Step-3: Minimize regedit, go to windows explorer. Create C:\FusionLog folder

Step-4: Run app which is crashing to see which dll is failing.

Step-5: Check FusionLog folder see any dll report. 
 
Step-6: IMPORTANT: Once you done genrating log files, Go to registry again and set ForceLog=0 and LogFailures=0 (Disable logging)

Then just browse the folder and look for the HTML with DLL name that failed to load, e.g. ZappySys.Json, and examine it.

More info: http://stackoverflow.com/questions/255669/how-to-enable-assembly-bind-failure-logging-fusion-in-net

Contact Us

If you have more question(s) feel free to contact us via Live chat or email to [e-mail]

https://zappysys.com/support/