NGWS SDK Documentation  

This is preliminary documentation and subject to change.
To comment on this topic, please send us email at ngwssdk@microsoft.com. Thanks!

Sending and Serializing Messages

A message in Microsoft Message Queuing consists of a body and a set of properties. Message bodies can contain text or any form of binary information, and can be encrypted. In the NGWS frameworks, you set a message's body and properties programmatically, either by setting property values in the Property window or by setting the required values in code. A message, including its body and all specified properties, cannot be bigger than 4 megabytes (MB) in size.

You can create and send messages with your MessageQueue components. Messages created in the NGWS frameworks can be sent to any public, private, journal, dead letter, or transactional queue.

For information about See
Sending simple messages as parameters of the Send method Sending Simple Messages
Sending messages using the Message object to fine-tune the message content and processing Sending Complex Messages
Sending a message to a queue that is not currently online Sending Messages to Disconnected Queues
Requesting acknowledgment messages to indicate whether your message successfully reached its destination Requesting Acknowledgment for a Message
Storing copies of the messages you send in a journal queue Storing Messages in a Journal Queue
Sending a series of messages together in a transaction, in which all of the messages are either successfully delivered or not sent. Processing Messages Transactionally
Sending a dataset as a message Serializing a DataSet into a Message
Setting default properties to be applied to all messages you send Default Message Properties
Serializing objects data into and de-serializing them out of a message Message Serialization