The Reactive Extensions for .NET
Catch us in the #rxnet channel over at http://reactiveui.net/slack
Ix Async 4.0 has a breaking change from prior versions due to being the first LINQ implementation to support the new C# 8 async streams feature. This means for .NET Standard 2.1 and .NET Core 3 targets, we use the in-box interfaces for
IAsyncEnumerableand friends. On other platforms, we provide the implementation, so you can use
await foreachand create async iterators as you would expect. The types will unify to the system ones where the platform provides it.
There are many breaking changes here; a full set of changenotes is on the way.
Rx.NET v5 is required for .NET 5 support of CSWinRT; earlier versions of Rx won't work correctly. To get the Windows API, you need to use the latest Windows SDK (19041), though you can target earlier versions of Windows.
Breaking changes In Windows, since the
net5.0-windows10.0.19041target now supports all Windows desktop object models, on UWP
DispatcherObservableand releated SubscribeOn/ObserveOn were renamed to be
ObserveOnCoreDispatcher. This reflects the OS type names.
Dispatcherrefers only to the WPF type.
Rx 5.x supports the following platforms
Support for UWP 10.0 has been removed.
System.Reactive. To prevent breaking existing code that references the v3 libraries, we have facades with TypeForwarders to the new assembly. If you have a reference to a binary built against v3.0, then use the new
Rx 4.1 supports the following platforms
Notably, Windows 8, Windows Phone 8 and legacy PCL libraries are no longer supported.
The NuGet packages have changed their package naming in the move from v2.x.x to v3.0.0 * ~~
Rx-Main~~ is now
Rx-Core~~ is now
Rx-Interfaces~~ is now
Rx-Linq~~ is now
Rx-PlatformServices~~ is now
Rx-Testing~~ is now
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.
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
IObservableinterface notifies the subscribed
IObserverinterface 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) and single-value asynchronous computations (
Task) as the following diagram shows:
|Single return value||Multiple return values|
git clone https://github.com/dotnet/reactive
Some of the best ways to contribute are to try things out, file bugs, and join in design conversations.
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.
System.Reactive is part of the .NET Foundation. Other projects that are associated with the foundation include the Microsoft .NET Compiler Platform ("Roslyn") as well as the Microsoft ASP.NET family of projects, Microsoft .NET Core & Xamarin Forms.
New York, USA
Daniel C. Weber