TSUtility.lib

[pschroeder]

I recently started using TestStand 2017 and LabVIEW 2017 for a project that had previously been run using the 2014 version.  I have found that the TSUtility.lib which is created when TestStand launches (in the C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\addons\TestStand directory) has the VIs in LabVIEW 2012.  So every time the top level VI calls the TestStand API VIs, they have to be recompiled.  Is there a way to get TestStand to create the .lib VIs in LabVIEW 2017.  Thanks.

[pulidotech]

I don't think so.  I recommend a mass compile on the [LabVIEW 2017]\vi.lib\addons\TestStand directory after installing LabVIEW and TestStand.

Pulido Technologies LLC

[pschroeder]

The mass compile did what I needed.  Thanks for the help.

[RoxtheFox]

Hey,

With TestStand 2017, we start shipping the VIs as source only so you will need to compile it only once for your LabVIEW version.