Communicate Between View Models with Observer Pattern - WPF C# MVVM

How to keep your View Models decoupled from each other and still allow them to communicate / send data to other View Models.

the problem - 00:00
diagram of solution - 00:42
sample app - 01:41
creating a messenger - 04:13
using the messenger - 22:15
summary - 29:05

[tomma]

This is also a great video demonstrating TDD.

[delarosomccay]

I haven't seen the service locator pattern implemented before for the DataContext. I love it! I have seen so many other attempts at parameterized constructors for DataContext, and none of them really pass the smell test. This one is perfect and can be unit tested easily. It can be easily mocked and, therefore, unit tested.

[lmanes]

I felt a little lost, but that's my own fault. I have a poor knowledge on these topics and your video guided me to a new learning path. Thank you!

[RebaiMoez]

Cool implemetation with real TDD approch

[lech]

Great explanation and video tutorial. Keep up the good work, there should be more content like this, thanks!

[niki]

Great video thanks so much for the effort!

[freddycancino]

Hi Jason, thank u shared, in this example is integrate dispose?

[alexeysavelyev]

Great tutorial! Can you explain hot to send a command to another view model?

[Postoronnim_B]

Jason, thanks for useful content. It's a pity, really, that you decide to make a pause. This messenger is your interpretation of pattern Mediator, am I right?

[habibi]

Great video. What framework are you using for dependency injection?