Book Image

Reactive Programming for .NET Developers

Book Image

Reactive Programming for .NET Developers

Overview of this book

Reactive programming is an innovative programming paradigm focused on time-based problem solving. It makes your programs better-performing, easier to scale, and more reliable. Want to create fast-running applications to handle complex logics and huge datasets for financial and big-data challenges? Then you have picked up the right book! Starting with the principles of reactive programming and unveiling the power of the pull-programming world, this book is your one-stop solution to get a deep practical understanding of reactive programming techniques. You will gradually learn all about reactive extensions, programming, testing, and debugging observable sequence, and integrating events from CLR data-at-rest or events. Finally, you will dive into advanced techniques such as manipulating time in data-flow, customizing operators and providers, and exploring functional reactive programming. By the end of the book, you'll know how to apply reactive programming to solve complex problems and build efficient programs with reactive user interfaces.
Table of Contents (15 chapters)
Reactive Programming for .NET Developers
About the Authors
About the Reviewer

Chapter 3. Reactive Extension Programming

This chapter will lead readers through the first steps in Reactive Extension (Rx) programming. We will give an overview of the Rx architecture with information on how to configure our application to use the framework and how to use its main components.

We will cover the following arguments:

  • Setting up Rx.NET

  • Marble diagrams

  • Subjects

  • Transforming operators

  • Combining operators

  • Filtering operators

  • Mathematical operators

  • Logic operators


The NuGet package names have been changed. The Rx-* and Ix-* packages have been renamed to match their library names, keeping inline with the rest of .NET Core.

  • Use System.Reactive instead of Rx-Main

  • Use System.Interactive instead of Ix-Main

  • Use System.Interactive.Async instead of Ix-Async