This video show how an existing application can be modified to move functionality into a separate assembly. Proper naming conventions will be discussed, as well as the ConfigureAwait method, which can be used to avoid unnecessary marshaling of data to the UI thread.
Watch this video on microsoft.com

In this episode we are going to take a look at another refactoring technique, the Extract Interface technique. This technique allows you to extract an interface from a class in order to break your concrete dependencies. By doing this you can provide yourself with better testing support as well as a better layer of abstractions.
http://www.dimecasts.net/Content/WatchEpisode/163

These two videos show how to use the refactoring tools in Visual Studio.
Video Part 1
Video Part 2

Nature abhors a vacuum.  It turns out she also abhors static dependencies (I have my sources).  Static dependencies are the modern-day globals, often exposed through classes named “Helper”.  I’ve certainly been guilty of overusing static dependencies in the past, with classes like “LoggingHelper”, “SessionHelper”, “DBHelper” and so on. The problem with static dependencies is that they are opaque to the extreme, enforcing a strong coupling that is impossible to see from users of the class.  To demonstrate techniques for eliminating static dependencies, Ray Houston and Jimmy Bogard created a short …

In this episode we are going to take a look at a refactoring technique outlined in detail in working effectively with legacy code. We will walk though this technique and take a look at how it can help you to create better and more maintainable code.
http://www.dimecasts.net/Content/WatchEpisode/134