http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Chris, I did something similar, except that I used MarkMissing() ;-) http://ayende.com/2530/the-auto-mocking-container#comment4http://ayende.com/2530/the-auto-mocking-container#comment4Tue, 12 Jun 2007 17:04:34 GMTWhat I ran into was that the AutoMockingContainer would detect the ValidatorRunner as a dependency of the Controller (because it is a public writeable property on Controller) and try to resolve the dependency by creating a mock which fails because no ctor args are passed to the call to DynamicMock<> I wound up modifying the AutoMockingDependencyResolver to return false if the mocking strategy is "NonMocked" so that the container could decide it was an optional dependency and ignore it. http://ayende.com/2530/the-auto-mocking-container#comment3http://ayende.com/2530/the-auto-mocking-container#comment3Tue, 12 Jun 2007 16:11:27 GMTChris, I don't have the Validator Running as a component in the container, so I haven't run into it. http://ayende.com/2530/the-auto-mocking-container#comment2http://ayende.com/2530/the-auto-mocking-container#comment2Tue, 12 Jun 2007 15:49:33 GMTDid you run into any problems with ValidatorRunner? When I tried to use this with controllers it kept trying to create the validator runner which doesn't have a default constructor and would fail. http://ayende.com/2530/the-auto-mocking-container#comment1http://ayende.com/2530/the-auto-mocking-container#comment1Tue, 12 Jun 2007 15:06:33 GMT