Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Among other things, .NET's Reactive Extensions simplify concurrency management.

From what I've heard, .NET 4.5 will simplify concurrency management with things like the await keyword.

My Question:

  • Will .NET 4.5 make the Reactive Extensions obsolete?
  • Or is Microsoft expected to pitch the .NET 4.5 additions as an alternative way to approach asynchronous and concurrent programming?
share|improve this question
See here for a complete answer to your question:… – Robert Harvey Nov 4 '11 at 17:38
@RobertHarvey Although that video is still valuable and informative,… goes over the integration with .NET 4.5 and is more up to date with the latest version. – Richard Hein Nov 4 '11 at 22:41

The newest release of Rx Experimental supports the new .NET 4.5 features and integrates more seamlessly with async/await and Tasks. So, the answer is no, .NET 4.5 doesn't make Rx obsolete, it makes it better. Take a look at for information on the integration with Tasks, especially under the post entitled "Prefer Async Policy". Task is best used for single values, Observables work great for streams. It depends on what you are doing.

share|improve this answer

Both serve complimentary needs, Rx being an event stream processing library, and the new .NET 4.5 features focusing on single-value asynchrony. Watch the C9 video for more details.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.