Knowledge Base Article

Home Page > Knowledge Base > Spira Platform > RemoteLaunch

Article How to enable assembly bind failure logging (Fusion) in .NET

by Adam S on Friday, September 18, 2015

Sometimes when using RemoteLaunch with a specific plugin (e.g. Selenium), you may get an error such as:

Could not load file or assembly 'WebDriver, Version=, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

The way to debug this kind of error message is to enable Microsoft .NET Fusion Logging to get more information as to which dependency could not be loaded. This article explains how to turn this on.
To enable Fusion logging in .NET, you need to do the following:
  • Open up the Windows Registry Editor (RegEdit.exe) and add the following keys:
DWORD ForceLog set value to 1
DWORD LogFailures set value to 1
DWORD LogResourceBinds set value to 1
String LogPath set value to folder for logs (e.g. C:\FusionLog\)

  • Make sure you include the backslash after the folder name and that the Folder exists.
  • You need to restart the program that you're running to force it to read those registry settings.
  • You can now locate the logs in C:\FusionLog and provide to Inflectra support who will help determine the cause.

Note: If you have the Windows SDK installed on your machine, you'll find the "Fusion Log Viewer" under Microsoft SDK\Tools (just type "Fusion" in the start menu on Vista or Windows 7/8). Launch it, click the Settings button, and select "Log bind failure" or "Log all binds".

Article Info
Last Updated: 9/18/2015
Article ID: KB171
# Views: 1596
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2016 | Licensed to Inflectra Corporation.