Having binding issues? No not that sort...

So more for my own poor memory, we have a project where references will throw errors like "The located assembly's manifest definition does not match the assembly reference." Not terribly useful.

But MS has a tool that can aid in diagnosing these issues, Fusion Log.

  1. Open up a VS (2k8 or 2k10) command prompt.
  2. Type fuslogvw.exe
  3. You should now see:
    Fusion Log Blank
  4. Next run your program, this can even do this from a test project. To isolate the issue just run the relevant test method via "Run Tests in Current Context"
  5. Click on the Refresh button and the list of bindings should show up:
    Fusion Log w/ Data
  6. Highlight an entry and click on View Log. It will give more details about what was loaded and hopefully a better error message for diagnosing why the module isn't loading.

That's it for now...