Did you ever use fusion logs? its an indispensable troubleshooting tool

Like I said in my previous article fusion logs are surely an indispensable tool when you are working with .NET (especially when you are troubleshooting).

Whenever you are running any assembly binding issue use fusion logs. What is 'fusion' anyways ? ..find out! that's a test for you :) 

There are two ways to take a fusion log:

1) Using tool fuslogvw.exe (try pronouncing it ;))

2) Using registry  ..let me know if you want to know about it !

 

Suzanne documented  more about debugging assembly load failures in great detail  ..

 

Here is the moral of the story:

Fusion logs will describe the binding failure (if this is due to an assembly binding failure, instead of a loading failure after the file is found). The exception may already include the log. If not, to get it, run fuslogvw.exe. If you don't have fuslogvw.exe already, install the Framework SDK.

• For pre-v2.0: click on "Log Failures." If this is an ASP.NET or .NET Windows service app, select the Custom option and using regedit, set [HKLM\Software\Microsoft\Fusion\LogPath] to point to an existing directory (like c:\mylogs, not c:\). If you need to log all binds, not just failing ones, set [HKLM\Software\Microsoft\Fusion\ForceLog] as a DWORD value to 1.
• For v2: click on "Settings," then choose "Log bind failures to disk" if you only care about the failures or "Log all binds to disk" if you want to see all binding requests.
• To turn on failure logging during a test run instead of by hand, have your script set [HKLM\Software\Microsoft\Fusion\LogFailures] as a DWORD value to 1 using regedit.

 

Technorati tags: Microsoft Blogger, Fusion, Fusion Log, Assembly Binding Issue, Troubleshooting

del.icio.us tags: Microsoft Blogger, Fusion, Fusion Log, Assembly Binding Issue, Troubleshooting