AutoMoq is an “auto-mocking” container that automatically creates for Moq any fake objects that are necessary to instantiate the class under test. You can access those fakes through the mocker or you can just ignore them if they’re not important.

Amanda Laucher and Josh Graham present at an introductory level some of the most important elements of the .NET ecosystem: F#, M, Boo, NUnit, RhinoMocks, Moq, NHibernate, Castle, Windsor, NVelocity, Guerilla WCF, Azure, MEF.
http://www.infoq.com/presentations/The-State-of-the-Art-on-.NET

In this episode we are going to take at how to use Pex and Moles for .Net. Unit testing is great, but most free isolation frameworks require that your mocks implement an interface. But what do you do when the class you are trying to mock is static or sealed with no interface. If you can’t modify the class then your unit testing efforts are usually stuck. Moles, the new free isolation framework from Microsoft, supports mocking almost any CLR based class (including sealed and static classes).
http://www.dimecasts.net/Content/WatchEpisode/170

In this episode we are going to take a look at how to use manual mocks for testing. Often times when creating unit tests we need to work in isolation in order to cover the paths we are attempting to test. When we want to test in isolation you can use a testing technique where you mock out your dependencies. When using Mocks you can either do it manually (what we are looking at) or you can use a mocking framework like Rhino Mocks. Either way you achieve the same …

In this talk David Evans and Mike Scott discuss the effect architectural decisions have on application testability. They assert that a testable architecture is inherently a better architecture, and demonstrate how testability in itself is an essential dimension in any architecture because of its relationship to good architectural patterns and practices.
http://skillsmatter.com/podcast/open-source-dot-net/testable-software