Jeffrey van Gogh
-
New release of Rx for .NET & JS (v1.0.2617.0) available!Build 1.0.2617.0 07/15/2010
Rx.NET
- Fixed GC issue with ThreadPool Timer.
- Made lock in CompositeDisposable smaller.
- Fixed deadlock in ForkJoin when using Immediate scheduler.
- Changed order of arguments for Generate* operators to match C# for pattern based on feedback from C# Team.
- Changed...
-
New drop of Rx (.NET & JS) available
The Rx Team just released a new build of Rx, which contains the following changes:
Build 1.0.2441.0 04/14/2010Rx.NET:
- Added BufferWithTimeOrCount.
- Changed ForkJoin to take the last value from each source.
- Peformed FxCop naming cleanup work.
- Removed FutureDisposable in favor of MutableDisposable....
-
Samuel McAravey: Using Rx in the Real WorldMost C9ers will probably have watched a video or two of Erik and/or his team members talking about Rx. In these videos, we can see some great samples of how to use Rx. But how does Rx play out when used in a real world scenario?
In this video, Jeff talks to Samuel McAravey from SoftSource Consulting... -
Your Rx.NET Prescription Has Been RefilledToday, we released a new version of Reactive Extensions for .NET.
This new version is a good reason to end the long video silence on C9. Here, Wes, Bart, and Jeff discuss the various changes in this release, why it took so long, and what we have been doing these last couple of months.
Rx can be... -
Jafar Husain: Silverlight Toolkit and Rx, Part 2Jafar explains how the Silverlight Toolkit uses Reactive Extensions. Jafar was one of the early adopters of Rx, in fact the Silverlight Toolkit was the first product to redistribute Rx.
Yesterday in part 1, Jafar showed a sample of how his team uses Rx in the product codeIn part 2, Jafar...
-
Jafar Husain: Silverlight Toolkit and Rx, Part 1Jafar explains how the Silverlight Toolkit uses Reactive Extensions. Jafar was one of the early adopters of Rx, in fact the Silverlight Toolkit was the first product to redistribute Rx.
In part 1, Jafar shows how the Rx Team's DragDrop example inspired him to use Rx to implement a real... -
Wes Dyer: Controlling Concurrency in RxThe Rx team has received a lot of questions about Rx and concurrency, thread-affinity, timers and performance. In this video, Wes explains the major changes in the latest release of Rx.
These changes drastically improve the user experience. Your feedback inspired the future direction of Rx.
New... -
Reactive Extensions API in depth: RetryIn this episode of the Rx API in depth, Wes talks talks about the Retry operator.
Visit the Reactive Extensions DevLabs page to download and learn more about Rx. -
Reactive Extensions API in depth: RepeatIn this episode of the Rx API in depth, Jeff talks talks about the Repeat operator.
Visit the Reactive Extensions DevLabs page to download and learn more about Rx. -
Rx API in depth: Hot and Cold observablesIn this episode of the Rx API in depth, Wes talks talks about hot and cold Observables.
Visit the Reactive Extensions DevLabs page to download and learn more about Rx.
| Forum | Thread | Replies | Latest activity |
|---|---|---|---|
| Tech Off | IObservable, IObserver, [Observable] | 10 | Nov 17, 2009 at 6:10 PM |
Staff
Here is a list of Channel 9 staff members.
Wes Dyer and Jeffrey Van Gogh: Rx Virtual Time
Aug 30, 2010 at 10:41 AMhttp://blogs.msdn.com/b/jeffva/archive/2010/08/27/testing-rx.aspx contains sample code, that hopefully will give you a headstart. We're working on getting our tests shipping as well, but will take a bit more time..
Wes Dyer and Jeffrey Van Gogh: Rx Virtual Time
Aug 30, 2010 at 10:39 AM@N2Cheval,
you would create a scheduler that derives from VirtualScheduler, give it two type parameters that implement the absolute and relative part of your notion of time. For this to work, your notion of time will need to be able to :
Jeffrey Van Gogh: Testing Rx with Pex
Dec 16, 2009 at 3:16 PMan internal source control system from before TFS (we're all old school Microsofties who have the old system's shortcuts in our fingers
)
Jeffrey Van Gogh: Testing Rx with Pex
Dec 16, 2009 at 8:30 AMWe didn't integrate Pex with Tfs.
In our team we use a checkin system popular inside Microsoft that does verification before checkin. Source changes get packaged up, send to a server. The server kicks off a build with the code changes, starts up a bunch of vms, installs the product and runs test on it. Only if everything passes the code is checked in by the server.
In this system adding pex is very easy as you can write test scripts in any (scripting) language you want as long as there is a commandline to execute. Not sure how much work it would be to get it going in TFS...
Reactive Extensions API in depth: CombineLatest
Dec 10, 2009 at 9:02 PMYup aware of the volume (and lighting) issues, recording on a Flip right now, which is great for home videos but less ideal for these kind of videos, getting a more professional camera soon...
Thanks! Yes we'll definately bring the marble diagrams up with the doc team...
Reactive Extensions API in depth: CombineLatest
Dec 10, 2009 at 5:12 PMDefinately, we already have the videos for the upcoming week or so recorded, but we'll include that in the next batch we'll record..
CombineLatest is extremely useful in a scenario where you always need a pair of events e.g. you need to know the latest key pressed in combination of the latest position of the mouse cursor.
Reactive Extensions API in depth: Zip
Dec 09, 2009 at 9:47 PMThere is a Join operator that implements the Join-Calculus, we'll do a future video on that operator for sure!
Reactive Extensions API in depth: Zip
Dec 08, 2009 at 4:02 PMThat's actually what CombineLatest does. We're missing one that will not duplicate but does take the latest unused value (cache of one, with consumption), will talk to Wes and Erik to see if that would be a useful operator...
Reactive Extensions API in depth: Zip
Dec 08, 2009 at 12:30 PMZip will start caching. On Thursday we'll explain CombineLatest which is like what you're describing as the second option...
Reactive Extensions API in depth: Contract
Dec 07, 2009 at 12:22 PMHi JWeber,
Rx allows all of the above options. It really depends on what you're looking for. option 1 would be the default behavior. if you had used a AsyncSubject or ReplaySubject, you could get option 3. option 1 and 4 you'd have to implement manually using Observable.Create.
Hope this helps,
Jeffrey
See more comments…