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

A reference architecture (part 1) | Dunatis

The goal of this series is to show you an example how you could design a system. It’s kind of a reference architecture that I like to use (I have used it – a number of times in middle-sized projects, and I’m still quite happy about it), but it’s up to you to decide if you find some ideas to be usable in your specific environment.

Source: A reference architecture (part 1) | Dunatis

Fluent Assertions

Fluentassertions : Fluent Assertions is a set of .NET extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style test. We currently use it in all our internal and client projects, and it is used in many open-source projects. It runs on .NET 3.5, 4.0 and 4.5 (Desktop and Windows Store), Silverlight 4 and 5 and Windows Phone 7.5. And it supports the unit test frameworks NUnit, XUnit, MBUnit, Gallio and MSpec.

Source: Fluentassertions

ide – Visual Studio 2013 Update 2 – C# navigation bar drop down menus not working – Stack Overflow

The dropdown menus in the code editor stopped working in Visual Studio 2013 for me.
The problem is a bug when using multiple monitors and a “leftmost” monitor that is not the “main” display…

The solution is quite simple for now: make your leftmost monitor the main monitor.
A bugfix is coming, included in next Visual Studio update.

More info:

ide – Visual Studio 2013 Update 2 – C# navigation bar drop down menus not working – Stack Overflow.