reactive

Reactive Extensions

Channel	Rx	Ix
AppVeyor (home)
NuGet.org
MyGet (gallery)

Join the conversation

Catch us in the #rx and #ix channels over in the .NET Slack.

Get nightly builds

• NuGet v3 feed url (VS 2015+): https://dotnet.myget.org/F/rx/api/v3/index.json
• NuGet v2 feed url (VS 2012+): https://dotnet.myget.org/F/rx/
• Symbol server url: https://dotnet.myget.org/F/rx/symbols/

Breaking changes

The NuGet packages have changed their package naming in the move from v2.x.x to v3.0.0

• Rx-Main is now System.Reactive
• Rx-Core is now System.Reactive.Core
• Rx-Interfaces is now System.Reactive.Interfaces
• Rx-Linq is now System.Reactive.Linq
• Rx-PlatformServices is now System.Reactive.PlatformServices
• Rx-Testing is now Microsoft.Reactive.Testing

This brings the NuGet package naming in line with NuGet guidelines and also the dominant namespace in each package. The strong name key has also changed, which is considered a breaking change. However, there are no expected API changes, therefore, once you make the NuGet change, no code changes should be necessary.

A Brief Intro

The Reactive Extensions (Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators. Using Rx, developers represent asynchronous data streams with Observables, query asynchronous data streams using LINQ operators, and parameterize the concurrency in the asynchronous data streams using Schedulers. Simply put, Rx = Observables + LINQ + Schedulers.

Whether you are authoring a traditional desktop or web-based application, you have to deal with asynchronous and event-based programming from time to time. Desktop applications have I/O operations and computationally expensive tasks that might take a long time to complete and potentially block other active threads. Furthermore, handling exceptions, cancellation, and synchronization is difficult and error-prone.

Using Rx, you can represent multiple asynchronous data streams (that come from diverse sources, e.g., stock quote, tweets, computer events, web service requests, etc.), and subscribe to the event stream using the IObserver<T> interface. The IObservable<T> interface notifies the subscribed IObserver<T> interface whenever an event occurs.

Because observable sequences are data streams, you can query them using standard LINQ query operators implemented by the Observable extension methods. Thus you can filter, project, aggregate, compose and perform time-based operations on multiple events easily by using these standard LINQ operators. In addition, there are a number of other reactive stream specific operators that allow powerful queries to be written. Cancellation, exceptions, and synchronization are also handled gracefully by using the extension methods provided by Rx.

Rx complements and interoperates smoothly with both synchronous data streams (IEnumerable<T>) and single-value asynchronous computations (Task<T>) as the following diagram shows:

	Single return value	Multiple return values
Pull/Synchronous/Interactive	T	IEnumerable<T>
Push/Asynchronous/Reactive	Task<T>	IObservable<T>

Additional documentation, video, tutorials and HOL are available on MSDN.

Flavors of Rx

• Rx.NET: (this repository) The Reactive Extensions (Rx) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators.
• RxJS 4 / RxJS 5 beta: The Reactive Extensions for JavaScript (RxJS) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators in JavaScript which can target both the browser and Node.js.
• RxJava: Reactive Extensions for the JVM – a library for composing asynchronous and event-based programs using observable sequences for the Java VM.
• RxScala: Reactive Extensions for Scala – a library for composing asynchronous and event-based programs using observable sequences
• RxCpp: The Reactive Extensions for Native (RxCpp) is a library for composing asynchronous and event-based programs using observable sequences and LINQ-style query operators in both C and C++.
• Rx.rb: A prototype implementation of Reactive Extensions for Ruby (Rx.rb).
• RxPy: The Reactive Extensions for Python 3 (Rx.Py) is a set of libraries to compose asynchronous and event-based programs using observable collections and LINQ-style query operators in Python 3.

Interactive Extensions

• Ix.NET: (included in this repository) The Interactive Extensions (Ix) is a .NET library which extends LINQ to Objects to provide many of the operators available in Rx but targeted for IEnumerable.
• IxJS: An implementation of LINQ to Objects and the Interactive Extensions (Ix) in JavaScript.
• IxCpp: An implantation of LINQ for Native Developers in C++

Applications

• Tx: a set of code samples showing how to use LINQ to events, such as real-time standing queries and queries on past history from trace and log files, which targets ETW, Windows Event Logs and SQL Server Extended Events.
• LINQ2Charts: an example for Rx bindings. Similar to existing APIs like LINQ to XML, it allows developers to use LINQ to create/change/update charts in an easy way and avoid having to deal with XML or other underneath data structures. We would love to see more Rx bindings like this one.

Contributing

Source code

• Clone the sources: git clone https://github.com/Reactive-Extensions/Rx.NET.git
• Building, testing and debugging the sources

Contribute!

Some of the best ways to contribute are to try things out, file bugs, and join in design conversations.

• How to Contribute
• Pull requests: Open/Closed

Looking for something to work on? The list of up for grabs issues is a great place to start.

This project has adopted a code of conduct adapted from the Contributor Covenant to clarify expected behavior in our community. This code of conduct has been adopted by many other projects. For more information see the Code of conduct.

.NET Foundation

This project is part of the .NET Foundation along with other projects like the class libraries for .NET Core.