Silverlight TV 79: Data Binding Debugging
Description
In this episode, Jesse Liberty explains how Reactive Extensions work with Silverlight and Windows Phone. In order to simplify the code, Jesse suggests using Reactive Extensions whenever you are deep into using asynchronous programming. He covers exactly what Reactive Extensions are, why you'd want to use them (or not), how they relate to LINQ, and what you should know before using them. And of course, Jesse offers some tips and tricks.
Relevant links:
- John's Blog and on Twitter (@john_papa)
- Jesse's blog and on Twitter (@jesseliberty)
Follow us on Twitter @SilverlightTV or on the web at http://silverlight.tv
Share
Download
Download this episode
- High Quality WMV (166.3 MB)
- MP3 (10.4 MB)
- Mid Quality WMV (115.3 MB)
- High Quality MP4 (374.0 MB)
- Low Quality MP4 (52.8 MB)
More episodes in this series
Silverlight TV 81: Four Great Windows Phone UX Tips
Related episodes
Jafar Husain: Silverlight Toolkit and Rx, Part 2
Jafar Husain: Silverlight Toolkit and Rx, Part 1
Episode 17: ReactiveUI with Michael Stonis
Episode 447: Jon DeJong on JavaScript Observables
@MSFTReactor Weekly - Guest: Ian Sinnott - JavaScript and React Discussion
CodeChat 050 - Observables Everywhere!
MVA Monthly: November 2015
Bridging the WinPhone to UWP Gap...
Episode 202: Michael Crump on Silverlight 5
Bart De Smet, Jafar Hussain, Matthew Podwysocki: Pragmatic Rx
The Discussion
-
androidi The video mentioned at the end
-
chief7 Great video. Very simple. Should help a lot of folks confused by RX. I know it helped me.
-
Gopi Great post. Can we use RX for silverlight application session timeout using mousemove event
-
SteveRichter Will we ever be able to do away with the UI thread? Or at least change C# to simplify the work of marshalling onto the UI thread.
-
Tuskan360 I just want to say that this video has totally revolutionised the way I'm developing my current application. I'm now building a database and synchronization service around reactive extensions to allow the UI to always respond to new data as soon as it's available and to allow it to be automatically persisted without any need for the programmer to explicitly save data.