Thanks for that info. Actually made me see that whole layer differently, thinking about interface DAL, instance DAL classes.
Testing with NMock or later would definitely be nice to have. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Brad Wilson Sent: Tuesday, August 14, 2007 8:01 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Stateless, static data access layer I suppose that depends on whether or not you want to test your system without a database. If things are tightly coupled to static methods on a specific class, there is no opportunity to replace it with something else for testing purposes (i.e., something that returns test data rather than talking to a database). On 8/14/07, Ron Young <[EMAIL PROTECTED]> wrote: > > Anything wrong with a DAL that is tightly coupled to stored procedures and > strongly typed datasets? If not then the first level of the DAL contains > those tightly coupled DAL classes with basically CRUD operations. > -- http://www.agileprogrammer.com/dotnetguy/ http://www.flickr.com/photos/dotnetguy/ http://www.last.fm/user/dotnetguy/ =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com