People are using some of the code and patterns from BackgroundMotion but I’m not sure if anyone is using the Core assembly directly. The Repository pattern is from Domain Driven Design (Evans) and is also documented on MartinFowler.com. Jimmy Nilsson also has a book about using domain driven design patterns with .NET.

Cheers,

Andrew.

Do you know if anyone documented the repository architecture or its use on a project outside of the background site? I am starting to use linq and I think the Core.dll code could speed up the development. But I don’t understand all the implications of its use, how to set it up on my code and I can’t seem to find anyone commenting on its use.

Thanks and best regards.

Thanks so much

You’re right, in this scenario, client code does know about the query expressions. One way to avoid this would be to create a layer of strongly-typed Repositorys that sit above this generic repository. However, if you do this you will lose the expressiveness of LINQ and so will have to create overloads/specifications that handle all your scenarios including sorting/paging etc.

Andrew.

is this better way or I missed something ?
CustomerRepository customerRepository = new CustomerRepository();
customerRepository.GetCustomerByName(”name”);