Debugging Calls to .NET Assemblies

.NET objects can exhibit unexpected behavior when LabVIEW has a different version of the assembly in memory than the version you want to use. To diagnose many of these .NET assembly conflicts, use the .NET Assemblies in Memory dialog box. Because this dialog box displays identifying information for the assemblies in memory, it allows you to verify if LabVIEW loaded the correct version of an assembly.

Complete the following steps to debug a call to a .NET assembly.

1. Determine the name, version number, and location on disk of the assembly you want LabVIEW to load. Ensure that the assembly is located within the search path that LabVIEW uses to locate assemblies.
2. Select View�.NET Assemblies in Memory to display the .NET Assemblies in Memory dialog box.
3. In the dialog box, locate the name of the assembly that you are trying to load.
4. Identify discrepancies between the assembly information in the dialog box and the identifying information of the desired assembly from step 1. If there are no discrepancies but LabVIEW does not reflect your most recent changes to the assembly, you might need to force LabVIEW to load the updated assembly.
5. Choose one of the following procedures for replacing the assembly in memory with the desired assembly.
   • Move the loaded assembly out of the assembly search path. This action forces LabVIEW to search for a different version of the same assembly.
   • Create a project configuration file to force LabVIEW to load the desired version of the assembly.
6. Close and reopen the projects that call the assembly. This action forces LabVIEW to unload the incorrect version of the assembly from memory and then to load the correct version.

   Note��If the VI that loaded the incorrect assembly is not part of a project, you must restart LabVIEW to clear the incorrect assembly from memory. NI strongly recommends that you use .NET objects only in LabVIEW projects.