#Rx extensions mostrecent code
The Rx library defines many Linq-like extension methods for manipulating IObservable sources of data, if you explore the above code via Intellisense, you will find many familiar methods ( Where, Select, Max, SelectMany. The ToObservable extension method returns an IObservable which is the Rx analogue of the IEnumerable interface in that it is a source of items. OddNumbers.Subscribe(number => Debug.WriteLine(number)) Īgain, the output of the above code is exactly the same as the Linq equivalent. Var oddNumbers = observableNumbers.Where(n => n % 2 = 1) Var observableNumbers = numbers.ToObservable() The following example shows some simple logic that finds all the odd numbers in a short sequence: Probably the easiest way to gain a quick understanding of Rx is to compare it with Linq. Once downloaded and installed, add references to System.Reactive, System.Observable and System.CoreEx and you are good to go.
#Rx extensions mostrecent download
The Rx library is available to download from the Rx DevLabs page: For a much more detailed tutorial, I would recommend reading “ DEVHOL202 – Curing the asynchronous blues with the Reactive Extensions for. Within the next few sections, I will provide a very brief overview of the Rx library, with the rest of the article focusing on practical and fun examples.
In practical terms, Rx provides a Linq-like API for handling events, allowing the developer to aggregate, filter and query them in a concise and familiar fashion. Rx is a library for composing asynchronous and event-based programs using observable collections. The “mission statement” for the Rx library can be summarised as follows: This article builds a couple of Rx powered Silverlight applications step by step, the final one being a Twitter / Bing Maps mashup that shows the location of snowfall in the UK based on users Tweets to the #uksnow hashtag. In this article, I will look at how the Reactive Extensions (Rx) library provides a common interface for asynchronous events and actions giving a consistent way to composite, orchestrate and marshal events between threads (and also have some fun creating a few cool mashups along the way!)
.jpg "rx extensions mostrecent")
NET UI frameworks lack a way of orchestrating these asynchronous activities. 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. The framework provides UI controls that fire events in response to user interactions. Whether reacting to user-input or handling responses from web services, Silverlight applications are typically asynchronous in nature. NOTE: You can view the Silverlight examples in action on my blog.
0 kommentar(er)
