Capture .NET Framework Assembly Binding Logs in LabVIEW

Use this procedure to capture .NET Framework assembly binding logs while reproducing an assembly loading issue in LabVIEW or a LabVIEW-built application. The logs show information about the assembly requested by the common language runtime (CLR), the locations searched, and the reported result of the binding operation. You can use this information to investigate missing dependencies, unexpected assembly locations, and assembly version mismatches.

To complete the procedure, you need LabVIEW, administrator access to Windows, and an installation of the Windows SDK, .NET Framework SDK tools, Visual Studio, or other supported SDK tools that includes the Assembly Binding Log Viewer (Fuslogvw.exe).

This procedure applies only to .NET Framework assembly binding on Windows. The Assembly Binding Log Viewer is not available on other non-Windows operating systems and does not apply to .NET Core or later implementations. For more information about the tool, refer to (External) Assembly Binding Log Viewer (Fuslogvw.exe). 

Verify the Prerequisites

1. Confirm that the assembly you are troubleshooting targets .NET Framework.

2. Confirm that Fuslogvw.exe is installed on the computer.

   • The tool is installed with (External) Visual Studio and can also be included with the Windows SDK and .NET Framework SDK tools. The exact executable location depends on the Windows version, the installed SDK and .NET Framework version. Common locations include:
     • C:\Program Files (x86)\Microsoft SDKs\Windows\v<SDK-version>A\bin\NETFX <framework-version> Tools\
     • C:\Program Files (x86)\Microsoft SDKs\Windows\v<SDK-version>A\bin\NETFX <framework-version> Tools\x64\
     • C:\Program Files (x86)\Microsoft SDKs\Windows\v<SDK-version>A\bin\
     • C:\Program Files (x86)\Microsoft SDKs\Windows\v<SDK-version>A\bin\x64\
   • In these paths, <SDK-version> represents the installed Windows SDK version and <framework-version> represents the installed .NET Framework tools version.

3. Confirm whether Windows, LabVIEW, and the .NET Framework assembly use 32-bit or 64-bit architectures, and run the corresponding version of Fuslogvw.exe.

4. Confirm that you have administrator access to Windows.

Open the Assembly Binding Log Viewer

1. Locate Fuslogvw.exe. 

2. Right-click and select Run as administrator.

   • Alternatively, you can launch it by opening Visual Studio as an administrator, going to Tools >> Command Line >> Developer Command Prompt, and running the following command: fuslogvw.

Configure Assembly Binding Logging

1. Create an empty local folder that will contain only the generated binding logs, such as: C:\FusionLogs.

2. In the Assembly Binding Log Viewer, select Settings.

3. Select Log bind failures to disk to capture failed binding operations.

   • If successful binding operations are also needed for comparison, select Log all binds to disk. This option can generate a large number of files and should remain enabled only while reproducing the issue.

4. Select Enable custom log path.

5. Under Custom log path, enter the log folder path created in step 1, and click OK.

6. In the main Assembly Binding Log Viewer window, under Log Location, select Custom.

Reproduce the Issue

1. Open the VI, LabVIEW project, or LabVIEW-built application in which the assembly loading issue occurs.

2. Perform the minimum set of actions required to reproduce the issue.

3. Record the approximate time at which the error occurs so that you can identify the corresponding log entry.

4. Close LabVIEW or the LabVIEW-built application after reproducing the issue.

Review and Save the Logs

1. Return to the Assembly Binding Log Viewer and select Refresh.

2. Locate the entry that corresponds to the affected LabVIEW process or LabVIEW-built application executable and the approximate time at which you reproduced the issue.

3. Select the entry and click on View Log.

4. Review the bind result, requested assembly identity, calling assembly, and locations searched by the CLR.

5. After collecting the logs, return to Settings, select Log disabled, and then click OK. 

6. Confirm that binding logging is disabled before continuing normal use of LabVIEW.

7. Preserve the relevant .htm files from the custom log folder if you need to provide the results to technical support. 

The custom log folder contains one or more .htm files describing the assembly binding operations captured while you reproduced the issue. Each relevant log shows the requested assembly identity, calling assembly, binding result, and CLR search locations.