C# – Why we should build with the highest warning level in .NET

" Why hasn't anyone come up with clustered build solutions in the .Net space?"

If compilation were to be clustered:

1. The compiler will have to first break the compilation into different threads which can be done on indepenent machines.
2. Send the code to different machines for compliation.
3. Wait till all machines have completed their task
4. Get the results from all machines in the cluster together.
5. Put together the results and link them up.

steps 1 and 5 are dependant on the nature of the project : Too many interdepencies and the number of distribuable tasks is drastically reduced. Step 2 and 4 depend on the status of your network. The time taken to send and recive the object files adds to the compile time and beats the benefit of clustering. Depending on the project you probably may end up with the same time for compiling on a single machine as you would for a cluster.

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 http://social.msdn.microsoft.com/Forums/en-US/rx/thread/23062737-e154-41af-99f6-45d819992254 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.