More from the dev that owns the loader...

 

If the exception message isn’t enough for you to determine what the problem is, try getting the Fusion log.  It will describe the binding failure (if this is due to an assembly binding failure, instead of a loading failure after the file is found).  Usually, the exception will include a Fusion log.  If not, to get the log: run fuslogvw.exe, click on ‘Log Failures’.  If this is an ASP.NET or .NET Windows service app, select the “Custom” option, and in regedit, set [HKLM\Software\Microsoft\Fusion\LogPath] to point to some directory (like c:\mylogs, not c:\).  If you need to log all binds, not just failing ones, set [HKLM\Software\Microsoft\Fusion\ForceLog] as a DWORD value, to 1.  Then, re-run the process.  Next, click ‘Refresh’ in fuslogvw, and a line should appear for each binding failure (or for each bind, if ForceLog is set).  Double-click on the line for this exception, and a web page should come up with the Fusion log.

 

If the file was found, it was loaded from the last path probed in the log (or from the GAC, if there is no path probed).