While not about custom collections, that article makes the following comment: "A quality DAL helps promote code reuse, is key to good performance, and is totally transparent."
This was my argument about configuration with iBATIS when using it in a DAL. Any configuration information that has to be tied to the application removes transparency of the DAL. The 1.0.0 Alpha- 07/10/2004 comment "sqlMap.config, providers.config must be place in the base directory of the application domain (same dir as app.config or web.config)" breaks this transparency. iBATIS should not require that anything iBATIS related must be tied to the application. Current changes are moving in that direction with the exception of providers.config which is still hard coded (as of 1.0.0). IMHO, Bob On 5/25/05, Roberto R <[EMAIL PROTECTED]> wrote: > Here's an article that some folks may find interesting (there's a part about > custom collections): > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/CustEntCls.asp > > Roberto > > > > On 5/25/05, Ron Grabowski <[EMAIL PROTECTED]> wrote: > > The latest version of Code Smith costs money - $49. When did that > > happen? > > > > --- Ron Grabowski <[EMAIL PROTECTED]> wrote: > > > > > > Yes, I am aware of Code Smith and QuickCode. In fact the template > > > collection came from a QuickCode submission. If you need more > > > functionality than what my single one form app does, by all means use > > > Code Smith or QuickCode. > > > >
