Reactive Extensions 6/5/2011 release available

We're pleased to announce the availability of the 6/5/2011 releases of the Reactive Extensions (Rx) for .NET.

• Stable release - Reactive Extensions (Rx) v1.0.10605, also available on NuGet (search for packages with prefix Rx-)
• Experimental release - Reactive Extensions (Rx) v1.1.10605 (Experimental Release), also available on NuGet (search for packages with prefix Rx_Experimental-)

Release Notes:

• Changed Windows Phone 7 version to no longer rely on features which are not available on that platform.
• Added CLSCompliant assembly attribute.
• Added AllowPartiallyTrustedCallers assembly attribute.
• Changed AsyncLock to use rethrow when exceptions occur.
• Replaced MutableDisposable and policy object by three types: SingleAssignmentDisposable (was SingleAssignment), MultipleAssignmentDisposable (was Replace), and SerialDisposable (was ReplaceAndDispose).
• Changed NewThreadScheduler to use a dedicated event loop for recursive scheduling.
• Removed unnecessary ForEach overloads. Use try-catch or statement composition to add code for OnCompleted or OnError, or leverage Do to perform side-effects.
• Changed Observable.Interval to not try to pump missed intervals.
• Added redist.txt file describing redistributable files.
• Stable Release available for .NET Framework 3.5, .NET Framework 4, Silverlight 4, and Windows Phone 7. NuGet packages available with prefix Rx-.
• Experimental Release available for .NET Framework 3.5, .NET Framework 4, Silverlight 4, Silverlight 5, and Windows Phone 7. NuGet packages available with prefix Rx_Experimental.

Give it a try and let us know what you think!

Comments

• Anonymous
  June 10, 2011
  I wonder how do you guys envision place of Rx among c# v.next feature set, TPL and TPLDataflow.

• Anonymous
  June 10, 2011
  The comment has been removed

• Anonymous
  June 10, 2011
  The comment has been removed

• Anonymous
  June 12, 2011
  >>You can also watch my "Demystifying the .NET Asynchronous Programming Landscape" talk Thanks Bart, I watched this presentation. Very nice. But I still can't get the whole picture. In CCR there were ports, which similar to IObservable can handle streams of messages/events. And I could easily compose these streams into eg. multiple readers-exclusive writer Arbiter. It seems that Rx should have similar/alternative solution too. I am going to check it out... But TPLDataflow reincarnated this reader-writer concept into exclusive schedulers. Many overlapping ideas which multiply a "pain of choice". Not an appropriate place to ask, but what Microsoft is planning for CCR and which library Rx/TplDataflow will be integrated into .NET Framework?

• Anonymous
  June 13, 2011
  What happened to System.Interactive?? I've been relying on EmumerableEx to provide a lot of missing LINQ operations for quite awhile now. Has it been separated from System.Reactive? Deprecated? There's no mention of it going away in the release notes, which surprises me given it's such a large change.

• Anonymous
  June 13, 2011
  Rx_Experimental-Silverlight depends on Rx-Main(1.1.10605), but Rx-Main is downgrades to 1.0.10605 instead Rx_Experimental-Main is released. I wonder Rx_Experimental-Silverlight should  depend on Rx_Experimental-Main.

• Anonymous
  June 13, 2011
  Blog post about Observable.Generate and Observable.Interval www.shirmanov.com/.../rx-framework-observablegenerate-and.html