NI TestStand Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
MimiKLM

Add the possibility to define the datatypes described in .net assemblies.

Status: Declined

I'm declining this due to lack of community support. I'll also mention that recent versions of TestStand support autocreating Enums in TestStand based off .NET Enum definitions.

Hi,

 

As in subject: add the possibility to define the datatypes described in .net assemblies.

 

Now developers, when they create veriables, can choose from between number, string, boolean, object reference and cointainers and arrays of these as well as from between DatabaseColumnValue, DatabesePropery Mapping, Error, Path, Expression, NI_LimitMeasurement, NI_MSgBoxFontData, NI_LV_DeployLibraryItem, NI_TDMSReference, IVI and LabVIEWAnalogWaveform, LabVIEWDigitalWaveform, LabVIEWDigitalData, LabVIEWDynamicData, LabVIEWClusterArray,LabVIEWIOControl.

 

These two groups of data types are called Custom Data Types ( number, string, boolean, object reference)  and Standard Data Types (rest of them).

 

I'd like to vote the .net types of data which are defined in .net assemblies were accessible from Standard Data Types menu along the LabVIEW datatypes.

1 Comment
WireWeaver
Active Participant
Status changed to: Declined

I'm declining this due to lack of community support. I'll also mention that recent versions of TestStand support autocreating Enums in TestStand based off .NET Enum definitions.

https://www.linkedin.com/in/trentweaver