Letters

摘要

A VSM reader responds to the September 2009 cover story on how to use the Repository pattern to eliminate dependencies in Test-Driven Development.rnThis approach makes a ton of sense to me if you're doing data access in the traditional AD0.NET fashion. But I'm not as clear about how to use it when you're using something like the Entity Framework (EF) for your data access (which is obviously another Microsoft-recommended best practice). It seems to me that you'd need to throw another two layers on top of the EF-generated objects for this to work (the repository plus the object facades), and that sort of misses the point behind letting the EF do the work for you. In other words, I'd appreciate any suggestions on how to use database mocking with the EF.