Veristand .net client API

[Des]

TestStand 2026 Q3's .NET step adapter runs user code on .NET 8 (CoreCLR). NationalInstruments.VeriStand.ClientAPI.dll only targets .NET Framework 4.8.

Teststand does not support the older API for calls. NI VeriStand Steps for TestStand is also not supported, possibly the same issue

[Mr._Jim]

Hi there and welcome to the forums.

No one has replied yet, so I'll attempt to start a conversation here, though I'm not sure how much help I'll be.

I'll admit that while I'm knowledgeable on LabVIEW and TestStand, I know very little about VeriStand.

If you don't get very far in this forum, you could also try the dedicated VeriStand forum: https://forums.ni.com/t5/VeriStand/bd-p/440

Based on limited research, a straightforward workaround is not looking promising, though I'll let someone else give a definitive answer.

You may have to develop a wrapper or some middleware to handle the ostensibly irreconcilable compatibility until VeriStand catches up.

For example, a server or daemon application that accepts textual commands and payloads, and in turn calls the VeriStand API for you for the subset of functionality you need for your application.

Then develop a client that sends and receives data and can be called from a TestStand step.

Hey, it's not much of an answer, but it is an answer. 😁

Hopefully someone more knowledgable will jump on this.

Jim

[ShockHouse]

ShockHouse_0-1787346970695.png

Not sure if you have seen this, but you have to set up Veristand to gRPC, then it's supposed to work for TestStand/Veristand if using the 2026 version of both.