The other day, I was attempting to debug a VS 2008 project, but kept getting a error binding to a specific assembly (one of mine). Despite the fact that my project had an explicit reference to version 3.x of dependent assembly (also located in the solution), Fusion (the .NET technology used to locate and load .NET assemblies) kept trying to load a previous version of the assembly.
In the course of trying to figure out the problem, I discovered the 'Assembly Binding Log Viewer' (Fuslogvw.exe), part of the Windows SDK, and found it to be highly useful in uncovering the problem. MSDN's article on Fuslogvw is here and Neil Kilbride has a blog entry here. For some reason which I don't yet understand, I had to set 'Log Categories' to 'Native Images' to get the info I needed. Note that others have said the default disk log location (IE's cache) is problematic, so they recommend setting a custom log location--Click the 'Settings' button, check 'Enable Custom Log Path' and fill in 'Custom Log Path'. You may also need to change 'Log Location' to 'Custom'.
No comments:
Post a Comment