Skip to content

Commit 7517969

Browse files
authored
Merge pull request #7018 from Particular/hazel-bohon-patch-1
2 parents f5db9f6 + f9b39fd commit 7517969

File tree

1 file changed

+4
-4
lines changed
  • nservicebus/messaging/claimcheck

1 file changed

+4
-4
lines changed

nservicebus/messaging/claimcheck/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -60,21 +60,21 @@ By default, blobs are stored with no set expiration. If messages have a [time to
6060

6161
There are two ways to specify the message properties to be sent using the `DataBus`:
6262

63-
1. Using the `DataBusProperty<T>` type
63+
1. Using the `ClaimCheckProperty<T>` type
6464
1. Message conventions
6565

6666
> [!NOTE]
6767
> `DataBus` properties must be top-level properties on a message class.
6868
69-
### Using `DataBusProperty<T>`
69+
### Using `ClaimCheckProperty<T>`
7070

71-
Set the type of the property to be sent over as `DataBusProperty<byte[]>`:
71+
Set the type of the property to be sent over as `ClaimCheckProperty<byte[]>`:
7272

7373
snippet: MessageWithLargePayload
7474

7575
### Using message conventions
7676

77-
NServiceBus also supports defining `DataBus` properties by convention. This allows data properties to be sent using the `DataBus` without using `DataBusProperty<T>`, thus removing the need for having a dependency on NServiceBus from the message types.
77+
NServiceBus also supports defining `DataBus` properties by convention. This allows data properties to be sent using the `DataBus` without using `ClaimCheckProperty<T>`, thus removing the need for having a dependency on NServiceBus from the message types.
7878

7979
In the configuration of the endpoint include:
8080

0 commit comments

Comments
 (0)