Windows Workflow underwent a major overhaul for .NET 4.0 and was largely a ground up rewrite. As part of that rewrite the workflow designer was also rebuilt; however it was fairly slow and in medium to large workflows was more than capable of crashing Visual Studio, taking all your unsaved changes with it and generally annoying anyone who had to use it for long periods of time.
In Visual Studio 2012 the workflow designer has been given some tender loving care and encouraged to behave more like a grown up.
For the workflow engine itself, Microsoft has added much needed support for state machines. Let's have a look at how to put one together.
Start Visual Studio 2012 and create a new Visual ...