Skip to content

Commit 5a48167

Browse files
jamesmcroftSergio0694
authored andcommitted
Updated docs for Unregister messages for registered handlers
1 parent 8331396 commit 5a48167

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

docs/mvvm/MigratingFromMvvmLight.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -669,7 +669,9 @@ Messenger.Default.Unregister<MyMessage>(this);
669669

670670
There is no direct replacement for the `Unregister<TMessage>(object, Action<TMessage>)` method in the MVVM Toolkit.
671671

672-
Alternatively, we recommend achieving a similar functionality with the MVVM Toolkit's `IMessenger` extension method `Unregister<TMessage>(object)`.
672+
The reason for the omission is that a message recipient can only have a single registered handler for any given message type.
673+
674+
We recommend achieving this functionality with the MVVM Toolkit's `IMessenger` extension method `Unregister<TMessage>(object)`.
673675

674676
```csharp
675677
// MvvmLight
@@ -695,7 +697,9 @@ Messenger.Default.Unregister<MyMessage, string>(this, nameof(MyViewModel));
695697

696698
There is no direct replacement for the `Unregister<TMessage>(object, object, Action<TMessage>)` method in the MVVM Toolkit.
697699

698-
Alternatively, we recommend achieving a similar functionality with the MVVM Toolkit's `Unregister<TMessage, TToken>(object, TToken)` method.
700+
The reason for the omission is that a message recipient can only have a single registered handler for any given message type.
701+
702+
We recommend achieving this functionality with the MVVM Toolkit's `Unregister<TMessage, TToken>(object, TToken)` method.
699703

700704
```csharp
701705
// MvvmLight

0 commit comments

Comments
 (0)