Rx and Ix 3.1.1

@onovotny onovotny released this Nov 21, 2016 · 2 commits to master since this release

Minor packaging update that ensures the NETStandard.Library meta-package isn't referenced by projects targeting the Desktop .NET Framework (4.5 and 4.6).


Rx and Ix 3.1

@onovotny onovotny released this Nov 3, 2016 · 9 commits to master since this release

The Reactive and Interactive Extensions v3.1 is a minor update to the libraries, consisting mostly of bug fixes and small enhancements.

The full list of items fixed/improved is available here, but below are some key highlights:

  • #205 Implement an assembly version strategy
  • #237 Rewrite of Ix Async to reduce memory allocations, make the code easier to read and fix many bugs
  • #273 Restored access to the PlatformEnlightenmentProvider.Current setter

Many thanks to @aelij for his excellent work in converting Ix Async to use async and await in #170.

Note for Desktop .NET Users: As part of #205, we now have a strict assembly versioning scheme in place. This may require binding redirects to work correctly. NuGet will generate these for you, so there's nothing you should have to do. If you're seeing issues, before reporting a bug, please verify you have AutoGenerateBindingRedirects enabled as described here. You may need to manually add it some older projects.


Reactive and Interactive Extensions for .NET 3.0

@onovotny onovotny released this Jun 21, 2016 · 243 commits to master since this release

Major update from version 2.2.5 adding support for .NET Core and the .NET Platform Standard. In addition to .NET Core support, a few bugs were addressed.

This update is the first after moving to the .NET Foundation. As such, there are a few noteworthy items:

  • The strong name key has been changed. The old key was a Microsoft key that could not be fully checked-in. The new key is checked in, allowing anyone to create custom builds easily.
    The package names have all changed
  • The NuGet package names have changed. The Rx-* and Ix-* packages have been renamed to match their library names, keeping inline with the rest of .NET Core. As the strong name key had to change, we did update the old packages as the new binaries incompatible due to strong name conflicts. They are fully source-code compatible.
    • Use System.Reactive instead of Rx-Main
    • Use System.Interactive instead of Ix-Main
    • Use System.Interactive.Async instead of Ix-Async
  • The supported platforms are .NET Platform Standard 1.0 and higher. This means the following minimum versions:
    • .NET Core App 1.0
    • .NET 4.5
    • Windows 8
    • Windows Phone 8 Silverlight
    • Windows Phone 8.1
  • On Visual Studio 2012 and 2013, NuGet 2.12 is required. On VS 2015, NuGet 3.4 or later is required.

As always, Rx and Ix have enhanced support per-platform, ensuring an optimal experience based on your target runtime.


Reactive Extensions for .NET version 2.2.5

@mattpodwysocki mattpodwysocki released this Aug 14, 2014 · 607 commits to master since this release

Minor update from version 2.2.4 to update the support for Universal applications. No new functionality was added for this release.

Closed Issues

  • #8 - Rx PCL target should be changed to portable-win8+net45+wp8+wpa81
  • #10 - Profile78 => Profile259, which is the same profile without WCF #10


Reactive Extensions version 2.2.4

@mattpodwysocki mattpodwysocki released this Apr 29, 2014 · 623 commits to master since this release

This is a minor update from Rx.NET v2.2.3 which includes two fixes. First is the support for Windows Universal libraries, and the second is ReplaySubject performance enhancements. With the help from the community, we are moving the Reactive Extensions forward and we have plenty more coming soon.

Windows Universal Support

With the release of Windows Phone 8.1, it is now possible to use the Windows Runtime to build apps that can target each form factor in the family of Windows devices. Using the universal Windows app project templates, you can now create one app where your business logic can be surfaced up through a user experience relevant to the device. This unified approach to app development means that your app has the potential to reach not just Windows phones and tablets, but Windows laptops and workstations as well.

Previously, our NuGet packages did not support Universal Windows Apps, but now, thanks to work from @paulcbetts, you can now write Universal Apps using the Reactive Extensions.

ReplaySubject Performance Enhancements

During the development of the Reactive Extensions version 2.0+, we have had a focus on performance as noted in Bart de Smet's post on the Reactive Extensions Team Blog. One of the overlooked areas of the performance work we did as Subjects.

We had the community step up in this regard to helping performance better on the ReplaySubject. The details are laid out in this very detailed blog post.

Many thanks to @LeeCampbell for his hard work for this feature.

Patterns in Using Generic Virtual Methods Issues

Some patterns in using generic virtual methods may cause increases in compilation time and size on disk when used with Microsoft pre-compilation technologies such as NGEN. This bug fix removes those patterns so that Microsoft pre-compilation technologies such as NGEN work better with the Reactive Extensions library. This change was tested and found to have no noticeable performance impact, other than stabilizing compilation times and the size on disk.

Closed Issues

  • #4 - Add Windows Universal support
  • #3 - Adding ReplaySubject perf improvements


  • 4be7549 - Updating import.targets for flattening
  • d56e5d1 - Add Wpa81 to BuildAll.proj
  • 7041c40 - Universal Unit Tests aren't A Thing yet
  • b94b695 - Add Configurations for Wpa81
  • 03368da - Add a Windows 8.1 + Windows Phone 8.1 Target
  • 7ea7fbb - Some patterns in using generic virtual methods may cause increases in compilation time and memory usage
  • 0815ac7 - Included multiple disposals to Replay UnitTests
  • 98ad574 - Remove comments
  • 5449869 - Adding ReplaySubject perf improvements
  • 044afd5 - Use background thread for long-running ThreadPoolScheduler