I am trying to develop a .NET 3.5 service application that uses:
- WCF for the service layer
- Business object layer to encapsulate our business logic (and isolate the service and data access layers)
- Linq-to-SQL for the data access technology
- Unity for dependency injection
- Enterprise Library 5 with the following:
- Validation Application Block
- Exception Handling Application Block
- Logging Application Block
We are also looking to follow TDD and want persistence ignorance (PI) as we may be changing data access technologies to either NHibernate or EF when we upgrade to .NET 4.0 later in the year and we want to minimize the impact such a change will have by isolating it to just the data access layer.
I have been working with the application for a little over a week now and have quite a bit of it working. I have yet to get the EHAB or LAB implemented successfully, validation is only partly implemented and PI is non-POCO based because we are required to support the designer (as opposed to using XML mapping). We are using the repository pattern with interfaces for PI.
Can anyone point me to some quality (real-world) example solutions using these technologies together? That’s probably the best way to address my questions and concerns because the articles I’ve referenced thus far only touch on one or two aspects of my solution and things aren’t working exactly the same as they describe when I wire all of this together.
Have you tried looking through p&p hands-on labs:
download sample solutions and instructions
These are pretty easy to work through, giving you guidance and usage patterns.