Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Sample14_AMQPMessage.md #39681

Merged
merged 1 commit into from
Nov 1, 2023
Merged

Update Sample14_AMQPMessage.md #39681

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion sdk/servicebus/Azure.Messaging.ServiceBus/samples/Sample14_AMQPMessage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This sample demonstrates how to interact with the underlying AMQP message used b

## Message body

The most common scenario where you may need to inspect the underlying AMQP message is in interop scenarios where you are receiving a message that has a non-standard body. The [AMQP specification](https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#section-message-format) allows three types of message body: a series of data sections, a value section, or a series of sequence sections. When using the `ServiceBusMessage.Body` property, you are implicitly using a single `data` section as the message body. If you are consuming from a queue or subscription in which the producer is sending messages with a non-standard body, you would need to the following:
The most common scenario where you may need to inspect the underlying AMQP message is in interop scenarios where you are receiving a message that has a non-standard body. The [AMQP specification](https://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-messaging-v1.0-os.html#section-message-format) allows three types of message body: a series of data sections, a value section, or a series of sequence sections. When using the `ServiceBusMessage.Body` property, you are implicitly using a single `data` section as the message body. If you are consuming from a queue or subscription in which the producer is sending messages with a non-standard body, you would need to do the following:

```C# Snippet:ServiceBusInspectMessageBody
ServiceBusReceiver receiver = client.CreateReceiver(queueName);
Expand Down