It seems to me that either fuslogvw.exe or fusion.dll has a serious bug.
If you try to do some CLR assembly resolver logging using the above mentioned tehnology you can end up with an empty fuslogvw.exe window.
If that's the case and you have set ForceLog  registry key to 1 and LogFailures to 1 and still only get the empty window, try deleting temporary internet files directory. As it seems, Fusion has a problem when certain number of files exist in there.
After purging the internet temp files directory, things returned to normal.
 HCLM/Software/Microsoft/Fusion/ForceLog, DWORD