Adds a certificate to the message

Adds certificate to message with the option to disable any intelligence

If true, a registration hint will be added to the message before sending.

Get/Set agent identity. Usually somthing like "MyClient.exe"

Get/Set the agent type. Current valid agent types are 0=AdvancedClient, 1=OsdCD, 2=Device, 4=IsvProxy, 8=IsvProxyClient

Get/Set the agent version. Defaults to null

Gets Attachments to the message.

Get/Set message body. This should never be empty except for some very special cases.

The client FQDN of the registeing machine. If unset, this will use the NetBiosName value.

Creates a clone of this message

IMPORTANT: This is not the same as Clone () () () () which is why this message type does not implement ICloneable. This does not behave the same as Clone () () () () . It is not recommended that any code outside of Messaging core code use this function without understanding how it works, what its limitations are, and why it's being used. Chances are if you're looking at this method, you probably want to use CloneByRef(IMessage)instead.

Clones a reference of a message. Use this for doing a copy of an existing message (especially of a different type) into this one.

IMPORTANT: This is not the same as Clone () () () () which is why this message type does not implement ICloneable. This does not behave the same as Clone () () () () . It is not recommended that any code outside of Messaging core code use this function without understanding how it works, what its limitations are, and why it's being used.

Clones a reference of a message. Use this for doing a copy of an existing message (especially of a different type) into this one.

IMPORTANT: This is not the same as Clone () () () () which is why this message type does not implement ICloneable. This does not behave the same as Clone () () () () . It is not recommended that any code outside of Messaging core code use this function without understanding how it works, what its limitations are, and why it's being used.

Creates confirmation request

Callback for changes for registration request creation before signing occurs

Creates a registration hint using the signing certificate assigned to the registration request and assigns the public property (RegistrationHint) with the generated hint. This method requires one of the following to be set: SmsId (checked first), SigningSmsId (checked second), RequestedSmsId (checked last)

Creates a registration hint using the signing certificate assigned to the registration request and assigns the public property (RegistrationHint) with the generated hint

Creates registration request

Callback for special changes for registration request creation before signing occurs

Invokes a statement within a thread-safe critical section

Internal handler for deserializing payload to its object format. This should only be called by external code under exceptional circumstances.

Performs discovery

Get/Set the discovery properties. This is not used in confirmation requests.

The encryption certificate used to include in the registration request

Retrieves X509-based certificate from message.

The Hardware ID of the registering machine. Hardware ID's are used to identify the machine hardware and are calculated using an implemention similar to Office's activiation engine. Any string provided will suffice as a hardware id, as long as it's unique to a machine.

Client's Internet status. Defaults to None (0)

The locale ID of the registering machine. Defaults to the locale ID of the calling machine.

Internal ID of the message.

The NetBIOS name of the registering machine. This is a required property.

On deserialization, this ensures validity checks are never performed.

Actions to run after the message is sent (asynchronous, use with care).

If true, message supports post-send actions

Actions to run before the message is sent (synchronous and blocking)

The priority for the message. This is only used for reference by senders and has no actual effect on the message

Helper method to perform a registration loop for a new client

Helper method to perform a registration loop for a new client

Gets or sets the registration hint to use for registering with the site server.

Registration request object

Get or set the type of registration message to send (ie: registration or confirmation). This affects the message returned from the MP.

Reply type encapsulated by this message

Get/Set the SMSID, leave null or emptystring to let the MP generate one for you if you are registering. Must be set if using for a confirmation request.

Callback to Sender for the message. This is null unless a message is in the process of being sent.

The sender type for the message. This is only used for reference by senders and has no actual effect on the message.

Sends a status message. This is a synchronous operation so it should be called from a separate thread to avoid blocking

Sends a status message. This is a synchronous operation so it should be called from a separate thread to avoid blocking

Sends message via the specified sender.

Sends message using the specified sender

Sends message via the specified sender.

Sends message via the specified sender.

Serializes the payload

Message settings and properties

Message settings

Get/Set the certificate used to sign the message and also serve as it's identity

Get/Set the SMSID that the signing the request on behalf. (Only use if you're registering AgentType 4 or AgentType 8)

Helper function that deserializes the object from the existing payload

Helper function that deserializes the object from the existing payload

Helper function that serializes the object to a payload

Gets/sets the site code to use for sending the message. Some messages require this.

Get/Set the SMSID to use for sending and signing the message.

If true, Serialize() will be called on send, and Deserialize() will be called on receive.

Default setting is true. Override to false with care.

Synchronizer to use for locking in thread-safe operations

Timestamp for the registration message

Validates all required message settings are present and meet the requirements. If this fails, it means that the message is almost certain to fail sending or being processed by the site/MP.