Friday, January 4, 2008 9:32 AM
First off, thanks to Willie for his excellent blog post walking through how to create a layered architecture with Sub Sonic. Although it did make it clearer what the steps were, it still didn't solve the issue I had raised earlier: the UI knowing and accessing information about the database connectivity mechanism which is still required in the web.config file (even if its just a path to where the actual config information is going to be found).
However, I want to bring this saga to an end for a couple of reasons:
1. I think the underlying discussion isn't specifically about Sub Sonic itself, but about architecture, separation of responsibilities, and how that gets implemented in a .NET application. These are the topics I'd like to focus my next few posts about.
2. Sub Sonic, as I stated in my previous post, is a great tool for doing what it does...which, if you aren't some "extremist Rock Star" as my buddy Will would say, means that it does a lot for making software development easier and creating a solid DAL with entities that are expandable. To rule out Rob's work because it *only * covers 99.99% of what *I'D* like it to would be foolish, and again I apologize to him and his devs if that was relayed in the prior post.
So with that let's put this baby to bed, altering the prior blog post title at Rob's request, and we'll move on to other topics.