In our last example, disaster finally struck our quaint little application. A strange defect showed up, which would be almost impossible to reproduce back on our developer machine. But because we've broken out our dependencies, our CustomerFinder became easier to test. When it became easier, actually...
We made quite a bit of progress separating out the concerns in Part 2, but there are still some issues with our current design. Other parts in this series include: Separation of Concerns - how not to do it Separation of Concerns by example: Part 1 - Refactoring away from static class Separation of Concerns...
Posted to
Jimmy Bogard
by
bogardj
on 06-26-2008
Filed under: Patterns, Refactoring, LINQ to SQL
In a recent article on layered LINQ applications in the latest ASP.NET PRO magazine (no link, you have to pay), the author proposes separating your application into three distinct layers: User Interface (UI) layer Business Logic Layer (BLL) Data Access Layer (DAL) I certainly would have agreed, at least...