The .Net Calls in the VeriStand LabVIEW API Broken When Opening the Custom Device Project

Updated Jun 23, 2026

Reported In

Software

  • VeriStand Custom Devices

Issue Details

While trying to build a VeriStand custom device, I noticed that some of the VeriStand LabVIEW API VIs were broken. I have VeriStand installed, but it seems like LabVIEW can't load VeriStand .NET DLLs like NationalInstruments.VeriStand.SystemDefinitionAPI.dll.

The dialog shown as the following when opening the project:

When I open the broken VIs, the .NET calls are missing the typical colors and the names are wrong:

How can I fix this?

Solution

  1. Copy the contents of this GitHub gist to a file next to your LabVIEW project, with the same file name as the project except with .config added to the end. If a file already exists, you can replace it (since the versions inside it are likely incorrect for your version of VeriStand, and the source of your pain). For example, if the project is named MyProject.lvproj, the new file would be named MyProject.lvproj.config.

  2. Replace the newVersion values (i.e. 8.0.0.0) in the *.lvproj.config file with the assembly version corresponding to the desired version of VeriStand. The values are shown below.

VeriStand Major VersionAssembly Version
20162016.0.0.0
20172017.0.0.0
20182018.0.0.0
20197.0.0.0
20208.0.0.0
20219.0.0.0
202310.0.0.0
202411.0.0.0
202512.0.0.0
202613.0.0.0
  1. Close the LabVIEW project and reopen it. Anecdotally it may be necessary to restart LabVIEW entirely.