Download source: RxTests.zip No, this is not an attempt to get spidered by putting every hot technology in the title! It’s actually self-induced attempt to give myself a brain hemorrhage by stuffing as many new to me technologies in one sample application as possible and trying to building it out …
I have an idea that it may be possible to predict build success/failure based on commit data. Why Scala? It’s a JVM language, has lots of powerful type features, and it has a linear algebra library which I’ll need later.
You! Yes, you, the one who is still scratching their head trying to figure out this Rx thing. As you learn and explore, please feel free add your own samples here, or tweak existing ones! Anyone can (and should!)
Introduction This article is an exploratory look into the Microsoft DevLabs project called Reactive Framework (Rx for short). I feel kind of weird saying this, but the demo solution that comes with this article will provide you nothing re-usable at all, but what it should hopefully do is give you an understanding of how Rx works.
This article is compatible with the latest version of Silverlight. This is part 1 of the series “Reactive Extensions in Silverlight”. 1. Introduction One of the coolest features which is part of .NET Framework and also available for Silverlight applications is the RX Framework. The arising interest around the RX Framework made me roll up my sleeves and start playing around this.
NOTE : You can view the Silverlight examples in action on my blog . Contents Introduction Whether reacting to user-input or handling responses from web services, Silverlight applications are typically asynchronous in nature. The framework provides UI controls that fire events in response to user interactions. There are also classes like the DispatcherTimer and WebControl that perform some background work, firing events which are helpfully marshalled back onto the UI thread.