repository-pattern

I have read almost all articles about Repository pattern and different implementations of it. Many of them judged bad practices (ex: using IQueryable<T> instead of IList<T> ) etc. that why i'm still stuck and couldn't end-up to the right one. So: Do I need Repository pattern to apply IoC in my MVVM applications ? If yes, What is the efficient IRepository implementation to EF Entities which is a good practice and better testable ? How can I test my Repositories and UnitofWork behavior ? Unit tests against in memory Repositories ? Integration tests ? Edit : According to answers I added the first

I've faced some troubles with context in EF in ASP.MVC2. I thought that best way to improve some operation on DataBase i've created Repository. My repo class adds, deletes, select many items so i don't need to write (using <name>Context = new (... etc ...) ) { ... } Repository eliminates initializing context for every operation, but don't dispose the context. What is the best way to manage contexts? If i create other repository class and try to do any operation which will need objects from both contexts there is a problem. Is there any other way or better way to implement repository, to manage

Having a parent object Employee with a list of Address child objects: class Employee { List<Address> addresses; } and a Repository method: void Insert(Employee); Should the code within this repository attempt to save the parent Employee as well as the child Address objects, or should separate repositories handle the parent and children objects? If separate repositories, then when saving the Employee object and its children within the client code, should this be separate calls at that level, combined in some sort of service or is there another alternative? The repository should handle the

I am trying to figure out how to tackle this problem. I have to insert some data into 2 tables lets call them Table A and Table B. Table A has these columns AId<PK> A1 A2 A3 Table B has AId<PK> A1 B2 B3 B4 Now my first question was should another repository call another repository? I don't think this will solve my current problem but I just want to know this for future reference? Now onto my problem. when I call a create in my repository layer(TableARepository) to Create Table A. I create right away the fields for tableB too. // linq to sql. TableA myATable = new TableA(); dbContext.myATable