Share via


Sending and Serializing Messages 

A message in Microsoft Windows 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. You set a message's body and properties programmatically, either by setting property values in the Properties 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 your applications can be sent to any public, private, journal, dead-letter, or transactional queue.

In This Section

  • Message Acknowledgement
    Provides an overview of the types of acknowledgement messages you can have your MessageQueue component generate.
  • Message Serialization
    Explains the two sides of serialization. First comes the process of converting an object or set of data into a message that can be sent to a queue. The other half is converting messages retrieved from the queue back into objects or data that your application can process.
Topic Location
How to: Verify Messages at Design Time Server Components in Visual Studio
How to: Verify Messages at Design Time Server Components in Visual Studio
How to: Verify Messages at Design Time Server Components in Visual Studio
  • Transactional Message Processing
    Describes the process of sending a series of messages together in a transaction, in which all of the messages are either successfully delivered or not sent.