Semiconductor Module and Veristand in TestStand 2024+

[ShockHouse]

What is the goal for the TestStand Semiconductor Module, and Veristand Steps in TestStand. Right now the currently released versions require you to use TestStand 2023. I'm guessing this is a limitation of those things using .NET Framework, so TestStand 2024+ is out of the question.

I have multiple stations coming up, that will need to use Semiconductor or Veristand in TestStand. I would rather use TestStand 2025 if possible, is there a roadmap or timeline when Semiconductor and Veristand will support modern releases of TestStand. 

[santo_13]

Is there any feature in TS2025 that you would like to use? if not I don't see a reason not to use TS2023

[ShockHouse]

I'd rather use .NET instead of .NET Framework on the backend, especially since all versions of TestStand going forward will be .NET. That way I can future proof my applications, custom code, and make them easier to update to newer versions without recompiling everything. 

Not to mention a lot of the report fixes in TestStand 2024+ are things my customers want (those specific things are outside of Semiconductor but in use with Veristand). Fixes like the on-the-fly reporting, pdf generation. And a big one we've had problems with is the deadlock issue with enums and LabVIEW that was fixed in 2025 Q2. 

[ZYOng]

Out of curiosity, would you mind sharing what kind of application are you working on that uses both STS and VeriStand?

[santo_13]

I think he has both applications separately but would like to be standardized on TS version within the org.

[ShockHouse]

Yup correct. Not using Veristand at the same time as the Semiconductor Module. But have different projects where Veristand is used for some, Semiconductor for another, LabVIEW/.NET for others, etc... So standardizing the year, and recommendations for customers.