Summary

In this chapter, we've seen how to use ReactiveUI, a library that takes the core principles of a technology (MVVM) and attempts to make them Rx-friendly. Since many parts of the .NET framework aren't designed with Rx in mind, a library to “bridge the gap” can enable code that is much cleaner. If you find yourself writing the same boilerplate code repeatedly, consider writing a bridge library like ReactiveUI. In this case, ReactiveUI enables writing code that is more straightforward, easier to test, and expresses code declaratively in an elegant way, as well as writing async UI code that works the first time and doesn't hang the UI.

While testability is mentioned as a significant benefit to Rx and ReactiveUI/MVVM in particular, this hasn't ...

Get Programming Reactive Extensions and LINQ now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.