Author: Andreas Plahn

C# Interactive Window · Wiki doc

The C# Interactive Window provides a fast and iterative way to learn APIs, experiment with code snippets, and test methods by giving immediate feedback on what an expression will return or what an API call does.

The C# Interactive Window is a read-eval-print-loop (REPL) with advanced editor support. It supports features like IntelliSense as well as the ability to redefine functions & classes. After entering a code snippet–which can contain class and function definitions at top-level along with statements–the code executes directly. This means you no longer need to open a project, define a namespace, define a Main method, add a Console.WriteLine() call to output your result, and add a Console.ReadLine() call in order to play with code. In other words, say goodbye to ConsoleApp137 or whatever ridiculously high number your Console Apps default to today!

Source: Interactive Window · dotnet/roslyn Wiki · GitHub

Unit testing faked async methods

With the addition of the async/await keywords in .NET Framework 4.5, many more methods will now return Task<TResult>.  For example, a web service method can now be created to return Task<TResult> so it is ready for the async/await keywords.  This brings up the question on how you can unit test these methods.

Read more: http://www.intertech.com/Blog/creating-a-task-with-a-known-result/#ixzz3xSNIAWB7