LabVIEW is Using a Different Version of the VeriStand .NET API Than Specified

Updated May 3, 2018

Reported In

Software

  • LabVIEW 2015 SP1 Full
  • LabVIEW 2017 Full
  • VeriStand 2015 SP1
  • VeriStand 2017 Full

Issue Details

Regardless of the .NET API version I select in the .NET Constructor in LabVIEW, it always returns to the most recent version that I have on my computer. For example, if I have version 2017.0.0.0 (version 2017), and specify that I want to use version 2015.1.0.0 (version 2015 SP1), it ends up using the 2017.0.0 version anyway.

Solution

You can explicitly tell LabVIEW which version to load using a .NET assembly binding redirection configuration file. You can find pre-made VeriStand .NET API redirection configuration files on the NI VeriStand Add-Ons GitHub repository. Be sure to check the README.md for exact instructions on how to use these files.

Note: Everything on the repository is provided as-is with no guarantee of functionality

Additional Information

LabVIEW will default to the latest version of the assemblies it can find when you open the project. More information on how LabVIEW handles loading different .NET assemblies can be found here.

WAS THIS ARTICLE HELPFUL?

Not Helpful