using FUSLOGVW.EXE on a machine with no Visual Studio installed

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.

Doing the above did not work for me..

I recommend doing the following instead:

In: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion

Add:

• ForceLog set value to 1 (DWORD )
• LogFailures set value to 1 (DWORD)
• LogResourceBinds set value to 1 (DWORD)
• LogPath (String) set value to folder for logs ie) C:\FusionLog\

Very straightforward.. and that worked for me! I use Windows 2012 R2.

Found this in: http://pauliom.com/2012/01/30/how-to-log-net-binding-errors-when-you-dont-have-fuslogvw-exe/

Thanks

As mentioned in an answer above and in comments, you need to do two things to get the fusion logger to run on a machine without Visual Studio:

1. Copy fuslogvw.exe to that machine. You can find it wherever you installed .NET (eg. C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\FUSLOGVW.exe)
2. Copy flogvwrc.dll to the same location as fuslogvw.exe on that machine. You can find it in the 1033 subdirectory where fuslogvw.exe was (eg. C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\1033\flogvwrc.dll)

Once you have fuslogvw.exe and flogvwrc.dll together in one directory, you can run the log viewer. You don't need registry changes or any other changes.