Ayende @ Rahien

Ayende Rahien commented on Repositories 101

Wed, 09 May 2007 10:51:14 GMT

You haven't moved the mocked instance to replay mode, probably.

Varela commented on Repositories 101

Wed, 09 May 2007 07:34:19 GMT

Ok, but as i understand, the next step should be initializing the IoC class with instance of mockedContainer: IoC.Initialize(mockedContainer); And after that, in our tests we should be able to retrieve from IoC our mocked instance of customerRepository: IRepository customersRepo = IoC.Resolve>(); But this step fails for me - instance is always null. I'm doing something wrong? Or i just have entered in "stupid mode" and i'm not seeing evident things? :) Anyway, thank you for the responce...

Varela commented on Repositories 101

Wed, 09 May 2007 07:34:19 GMT

Ayende Rahien commented on Repositories 101

Tue, 08 May 2007 21:20:18 GMT

The code above makes a few assumptions, that you are using Windsor, that you are using Rhino Common's repository, etc. Basically, the code in the setup is something like: mockedContainer = mocks.DynamicMock(); customersRepository = mocks.DynamicMock>(); SetupResult.For(mockedContainer.Resolve>()) .Return( customersRepository ) ;

Varela commented on Repositories 101

Tue, 08 May 2007 21:12:26 GMT

Can you please sketch the ideea how to setup mocks for sample that you provide? Sorry, i'm new to Rhino & Windsor, but i find these tools just great. I stuck some time with [SetUp] section of my test fixture, but still not able to wire together MockRepository, Repository, WindsorContainer & IoC . Thanks in advance. And thank you for your posts. You provide a really good content. You do a really good job.

Paulo Quicoli commented on Repositories 101

Tue, 20 Mar 2007 10:39:14 GMT

thanks for make things clear !

Ayende Rahien commented on Repositories 101

Tue, 20 Mar 2007 09:53:16 GMT

That may be a great solution to this, yes. I am concerned about the difference in implementation, but that puts a general query in the hand of the repository, and the burden of making it work is with the hands of the repository, not the app developer, which is as it should be.

Andrew Peters commented on Repositories 101

Tue, 20 Mar 2007 09:40:03 GMT

Having a truly generic repository becomes a bit easier with LINQ. I implemented a version of your Repository pattern on a recent project that used LINQ to SQL and was able to substitute an in-memory database no problems. Repository finders accept LINQ expressions that can be used to query either the database or in-memory collections.

Steve commented on Repositories 101

Tue, 20 Mar 2007 03:01:26 GMT

I agree, Please continue Ayende :) Thank you sir!

Christopher Bennage commented on Repositories 101

Tue, 20 Mar 2007 02:27:33 GMT

These sort of posts are really useful. Thanks.