I have CompanyController and DepartmentController: public class CompanyController : BaseBackendController
I have the following repository that I use for unit testing: public class MyTestRepository<T> { private List<T> entities = new List<T>();
So, I\'m developing some software, and trying to keep myself using TDD and other best practices. I\'m trying to write tests to define the classes and repository.
I saw this code work with LINQ to SQL but when I use Entity Framework, it throws this error: LINQ to Entities does not recognize the method \'System.Linq.IQueryable\'1[MyProject.Models.CommunityFeat
Should I be doing my automapping in my service layer or at my controller? I like the Idea of Repository - Raw data IQueryable type stuff with full domain(type) objects.
Currently im using EF and using its datacontext directly in all of my actions, but since i started reading about loose coupling and testability im thinking that thats not the best way to go. Im trying
i wish to create a repository pattern but with a WCF Rest Service which controls the data access.Can anyone confirm or help with my thinking / config.
When I started with Windsor I thought DI would be simple. Now it\'s causing me more and more confusion.
I have a WCF service which implemented using Repository and UnitofWork patterns. And now I am getting following error:
I have an ASP MVC application using LINQ to SQL for data access. I am trying to use the Repository and Unit of Work patterns, with a service layer consuming the repositories and unit of work.