Resolve Dependency Conflicts in VeriStand Custom Device APIs

Updated Aug 7, 2026

Reported In

Software

  • VeriStand
  • LabVIEW 2026 Q1
  • LabVIEW 2017
  • LabVIEW 2024 Q3

Issue Details

I have a custom device project that was originally built in LabVIEW 2017. When I open the project in LabVIEW 2024, it loads successfully without any dependency conflicts. However, when I open the same project in LabVIEW 2026 Q1, the VeriStand Custom Device API dependencies show conflicts instead of automatically loading from the installed location in the Program Files directory.

 

Solution

The issue can occur when the VeriStand Custom Device API dependencies are resolved from an incorrect location instead of the installed VeriStand directory.

To resolve the issue:

  1. Reinstall NI VeriStand 2026.
  2. Open the custom device project again in LabVIEW 2026 Q1.
  3. Verify that the VeriStand Custom Device API dependencies are loading from the installed VeriStand location under Program Files.
  4. Review the project dependencies to confirm that no references are resolving from unintended locations.

Reinstalling NI VeriStand 2026 refreshes the installed API files and allows LabVIEW 2026 Q1 to correctly resolve the VeriStand Custom Device API dependencies.

 

Additional Information

This behavior was observed with a custom device originally developed in LabVIEW 2017 and subsequently opened in newer LabVIEW versions.

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.