I am trying to develop a .NET 3.5 application application that uses:
- WCF for service level
- The level of the business object to encapsulate our business logic (and isolate the levels of access to services and data access)
- Linq-to-SQL for data access technology
- Unity for Injecting Dependencies
- Corporate library 5 with the following:
- Application block for verification
- Exception Handling Application Block
- Protocol Logging Unit
We also strive to keep tabs on TDD and want to maintain ignorance (PI), as we can change data access technologies in NHibernate or EF when we upgrade to .NET 4.0 later this year, and we want to minimize the impact such a change will have. isolating it only from the data access level.
I have been working with this application for a little over a week and have been working a bit. I have not yet received a successful implementation of EHAB or LAB, validation is only partially implemented, and PI is non-POCO, because we must support the constructor (as opposed to using XML mapping). We use a repository template with interfaces for PI.
Can someone point me to some qualitative (real) examples of solutions that use these technologies together? This is probably the best way to solve my questions and problems, because the articles I cited relate to only one or two aspects of my solution, and everything does not work as they describe when I put it all together.
source
share