'Declaration
 
<JetBrains.Annotations.ItemNotNullAttribute()>
<JetBrains.Annotations.NotNullAttribute()>
Public ReadOnly Property DataSetReaderMessageParametersCollection As Collection(Of UADataSetReaderMessageParameters)

'Usage
 
Dim instance As UASubscriberCommunicationParameters
Dim value As Collection(Of UADataSetReaderMessageParameters)
 
value = instance.DataSetReaderMessageParametersCollection

[JetBrains.Annotations.ItemNotNull()]
[JetBrains.Annotations.NotNull()]
public Collection<UADataSetReaderMessageParameters> DataSetReaderMessageParametersCollection {get;}

[JetBrains.Annotations.ItemNotNull()]
[JetBrains.Annotations.NotNull()]
public:
property Collection<UADataSetReaderMessageParameters^>^ DataSetReaderMessageParametersCollection {
   Collection<UADataSetReaderMessageParameters^>^ get();
}

Property Value

The value of this property cannot be null (Nothing in Visual Basic).

The individual elements of the property value cannot be null (Nothing in Visual Basic).

The reason why we need a collection of parameters, and not just one, is as follows: Imagine that the connection is described logically only (requiring resolution), but the filter is described physically (and will not be resolved). In this case, the message subscription parameters will not get resolved (because their resolution comes from the filter). But the resolution of the connection can sometimes result in connection with one transport, and sometimes in connection with a different transport. We therefore need to have a possibility to specify message parameters for *all* transports that the user needs with that logical connection.

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