Updating References to the Assembly

The example LabVIEW project was developed on a 64-bit machine using a 32-bit version of XJTAG with the bin directory (containing the XJIntegration binary and its dependencies) located at C:\Program Files (x86)\XJTAG 4.2\Bin. However a 32-bit version of Windows would install XJTAG in a different location. Installing a 64-bit version of XJTAG would also install to a different location. In these cases you must add the correct path to LabVIEW's list of VI Search Paths. This is done as follows:

  1. In LabVIEW, go to Tools > Options and click on the Paths category
  2. Select VI Search Path in the drop down list
  3. Click Browse and find the XJTAG Bin directory which is .
  4. Click Insert After then OK

This allows LabVIEW to locate XJIntegration.dll without prompting the user to find it manually each time it is required.

If you wish to resolve all references to the assembly (LabVIEW keeps hard-coded references in all VIs that use the assembly) for the whole project you must perform a 'Mass Compile' on the folder that contains the LabVIEW project. This is done as follows:

  1. Ensure that XJTAG example project is not open.
  2. In LabVIEW, go to Tools > Advanced > Mass Compile...
  3. Navigate to the top level directory of the project (i.e. the directory in which the LabVIEW project resides)
  4. Select Current Folder and run the mass compile.

Issues

A known issue is that a mass compile that updates the references to the XJIntegration.dll can break the PopulateTestFunctions.vi and the PopulateTestTree.vi; There is no real error however, the change of reference can cause a couple of .NET Invoke/Property nodes to think they cannot find the .NET method/property that should be called. To fix this the method or property must be re-selected.

In the XJTAG Multiple Test Runs.vi trace the error using the error list down to the offending invoke or property node. Right-click that node and re-select the method or property from the Select Method or Select Property menu. If these menu options do not appear it is because the offending node is further back in the execution. Trace the wire back and perform the last step on that node until you can reselect a method or property. As a result of this the VIs should then be able to be run.