I'm currently having some assembly binding problems on our development server. I want to investigate the problem a bit further with Fusion Log Viewer. Since there is no Visual Studio installed on the machine, I copied FUSLOGVW.EXE to a local folder and started it there.
Is this supposed to work or does it need something else? I don't get the impression the application is logging any failures (and yes I have the settings right).
Fuslogvw doesn't do the logging. The fusion loader does that. Fuslogvw just displays the log output. Are you getting any logs at all in the output directory you have configured?
Oh, and it should work on a machine that does not have Visual Studio installed.
You also need to create a LogFailures key in HKLM\SOFTWARE\Microsoft\Fusion with a DWORD value of 1 to turn on the log. You should set this value back to 0 when not testing otherwise it will keep populating the log. Create a folder eg. C:\fuslog and refer to it in the Custom log path in Settings in the Assembly Binding Log Viewer.
I wrote an assembly binding log viewer named Fusion++ and put it on GitHub. It writes the registry keys you need to have to activate the logging on your machine and parses the logs afterwards so you don't have to go file hunting.
You can get the latest release from here or via chocolatey (choco install fusionplusplus).
I hope you and some of the visitors in here can save some worthy lifetime minutes with it.
You might be using the wrong version of fuslogvw. check c:\program files\microsoft SDKs or c:\program files\Microsoft.net\SDK for a different version of the utility.
