repository-pattern

I am starting with DDD. I am a bit confused with the interaction between the several layers involved in a DDD application. Can I call my repositories from my presentation layer? If not do I have to replicate the CRUD functionality provided by the repositories in my service layer (which ofcourse will in turn use the repository for these functions)? What would be the best way to do this? What exactly do you mean by presentation layer? If you mean the Controller/Presenter, then it's perfectly fine. The rule of thumb that I've used is if the controller action is 4 lines of code or more I should

I have the following application structure, based on the onion architecture by Jeffery Palermo (ref link) . So my Core is not dependant on anything, my Infrastructure is dependent on my Core My Core has the Repository Contract and my Infrastructure implements it. The Implementation gets Injected by my IoC Container Core -Interfaces --IRepository<TDomainModel> -Domain --Person Infrastructure -Data --Repository<TDomainModel> (Implementation) -Entities --Ef.edmx So this wouldn't be a problem if I wrote out a concrete repository implementation (e.g a PersonRepository) because I know what type to

I'm trying to implement the repository pattern using entity framework code first rc 1. The problem I am running into is with creating the DbContext. I have an ioc container resolving the IRepository and it has a contextprovider which just news up a new DbContext with a connection string in a windsor.config file. With linq2sql this part was no problem but EF seems to be choking. I'll describe the problem below with an example. I've pulled out the code to simplify things a bit so that is why you don't see any repository pattern stuff here. just sorta what is happening without all the extra code

I have started translating a project into a generic repository and unit of work pattern. So far I have been able to reverse engineer all direct context references in the controllers to a generic repository; however, I am having trouble with the following two lines of codes: `context.Entry(ticket).Collection(i => i.TicketItems).Load(); ticket.TicketItems.Clear();` This is what my controller was doing before to remove any reference between a Ticket and a TicketItem . There is a many-to-many relation between Ticket and TicketItem . So those two lines of code is what I was using before to remove

I currently have a repository that is using Entity Framework for my CRUD operations. This is injected into my service that needs to use this repo. Using AutoMapper, I project the entity Model onto a Poco model and the poco gets returned by the service. If my objects have multiple properties, what is a correct way to set-up and then assert my properties? If my service has multiple repo dependencies what is the correct way to setup all my mocks? * - A class [setup] where all the mocks and objects are configured for these test fixtures?***** I want to avoid having 10 tests and each test has 50