Yes, it does impose you to use Rhino Mocks. All the properties such as Request, Response, Session, HttpContext, ... on the TestHelperBuilder class are stubbed with Rhino Mocks and are waiting for you to write expectations on them.
I'm not sure when this was changed, but the TestControllerBuilder now takes an optional IMockFactory argument. The problem I found with this is that if you don't pass one in, it defaults first to RhinoMocks and then to Moq, both as proxies. If you're using StructureMap, as I am, it will always use RhinoMocks.
I really wish there were a flag of some sort to tell the TestControllerBuilder which one to use.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.