References

Most LabVIEW references are not usable inside of TestStand and are treated as unsigned longs. Additionally, LabVIEW references cannot be used across LabVIEW environments. For example, if you obtain a VI reference as an output after calling a VI using an ActiveX Automation server and try to pass this reference to a VI running in a run-time engine, this reference will be invalid in the run-time engine environment.

An ActiveX Automation reference from LabVIEW is stored in a TestStand object reference, and the TestStand ActiveX/COM Adapter can use the reference. When you specify an object reference property as the value of an ActiveX parameter to a VI, TestStand passes the value of the property. When you pass a reference to a TestStand object, the VI can use the property object reference in conjunction with the TestStand API to get and set the values of properties in the object, to add properties to the object, and so on.

A .NET reference from LabVIEW is stored in a TestStand object reference. The .NET Adapter can use the .NET reference if the .NET objects derive from MarshalByRefObject or are serializable.

See Also

LabVIEW Data Types in TestStand

Mapping Parameters

Programming with the TestStand API in LabVIEW

Sharing .NET Objects Between LabVIEW and TestStand