I’m proud to announce that Reactive Extensions for .NET has joined the.NET FoundationFamily. While Rx.NET has been open source for a long time, this move signifies that the project is moving from one driven primarily by Microsoft to true cross-community ownership. Legends of .NET open source, Oren Novotny and Brendan Forster join Bart De Smet and Matthew Podwysocki as the new maintainers of the project so you know it’s in the very best hands in the business.
We’ll all be working to move things over in the next few days as we all get ready for the big 1.0 of .NET Core. In this guest post, Oren explains more about the move and what it means for the project.
Announcing Rx and Ix 3.0
The first thing to announce is that work has been ongoing to bring .NET Core support for Rx.NET and Ix.NET. The code is in a public beta form right now and you can check out the CI MyGet feed for regular builds. We’ll have an RC2-compatible build on NuGet.org shortly and expect to GA alongside the rest of .NET Core on June 27.
Learn more about Reactive Programming with Rx over at http://reactivex.io/
There are two breaking changes to note in V3:
- Rx has a new Strong Name Key. This means that code must be recompiled against this new version; binding redirects will not work. The good news is that the SNK is now checked into the repository, so you can create private builds that are fully signed should you need to. This was not possible before as the existing SNK was the same key as the .NET Framework.
- The NuGet package names have changed. The
Ix-*packages have been renamed to match their library names, keeping inline with the rest of .NET Core.
If you find any issues, please file them over on GitHub . After we’ve got the V3.0 release out the door we’re going to start working through the backlog that has built up in the project so please bear with us until the end of June while we get the initial community driven release out the door. Come on over if you want to help out!
Oren Novotny, Co-Maintainer, Reactive Extensions for .NET