public System.bool RequestorSCURole {get; set;}

public read-write property RequestorSCURole: System.Boolean; 

public function get,set RequestorSCURole : System.boolean

public: __property System.bool get_RequestorSCURole();
public: __property void set_RequestorSCURole( 
   System.bool value
);

public:
property System.bool RequestorSCURole {
   System.bool get();
   void set (    System.bool value);
}

'Declaration
 
Public Property RequestorSCURole As System.Boolean

'Usage
 
Dim instance As DicomContext
Dim value As System.Boolean
 
instance.RequestorSCURole = value
 
value = instance.RequestorSCURole

Property Value

Normally in DICOM, the requester of an association becomes the SCU, and the acceptor becomes the SCP, but there are some situations (notably Storage Commitment), where this relationship needs to be reversed (or it is possible for both applications to adopt both roles). In DicomObejcts, this is achieved using these properties, and is only possible (for outgoing operations) using an association based on an explicit DicomAssociation.

To propose reverse role negotiation, DicomContext items must be created explicitly, and the contexts' RequestorSCURole should be set to false, and the RequestorSCPRole should be set to true.

When accepting associations, DicomObjects's default action is to accept whatever roles are proposed by the requester, but this may be over-ridden in the AssociationRequest event by modifying these properties of any of the proposed contexts.

Once an association is established, these properties become read-only, but still reflect the arrangement negotiated.

Please note that these properties are shared between all contexts with the same AbstractSyntax (SOP Class), so changing one will change the value for any other matching contexts.

Target Platforms: .NET CLR 4.8 or higher