'Declaration
 
<DefaultValueAttribute(Mono.Cecil.CustomAttributeArgument)>
<DisplayAttribute(AutoGenerateField=False, 
   Order=2002, 
   ShortName="Value Type Code")>
<IgnoreDataMemberAttribute()>
<XmlIgnoreAttribute()>
Public Property ValueTypeCode As TypeCode

'Usage
 
Dim instance As UAAttributePointWriteParameters
Dim value As TypeCode
 
instance.ValueTypeCode = value
 
value = instance.ValueTypeCode

[DefaultValue(Mono.Cecil.CustomAttributeArgument)]
[Display(AutoGenerateField=false, 
   Order=2002, 
   ShortName="Value Type Code")]
[IgnoreDataMember()]
[XmlIgnore()]
public TypeCode ValueTypeCode {get; set;}

[DefaultValue(Mono.Cecil.CustomAttributeArgument)]
[Display(AutoGenerateField=false, 
   Order=2002, 
   ShortName="Value Type Code")]
[IgnoreDataMember()]
[XmlIgnore()]
public:
property TypeCode ValueTypeCode {
   TypeCode get();
   void set (    TypeCode value);
}

Property Value

When the type code is System.TypeCode.Empty, and the UAAttributePoint.AttributeId is equal to OpcLabs.EasyOpc.UA.UAAttributeId.Value, it means that the component will determine the type of the Value attribute from the DataType and ValueRank attributes of the node first. This can have negative implication on the performance, and introduces a dependency of the value written on the behavior of the OPC server itself.

Target Platforms: .NET Framework: Windows 10 (selected versions), Windows 11 (selected versions), Windows Server 2016, Windows Server 2022; .NET: Linux, macOS, Microsoft Windows