Yeah that looks different. According to the list page, there's only 2 members subscribed to that project ??? I've never used that.
--- Brandon Goodin <[EMAIL PROTECTED]> wrote: > DAAB is the Data Access Block. It is different than the Data Mapping > Block. > > Brandon > > On 5/27/05, Ron Grabowski <[EMAIL PROTECTED]> wrote: > > I believe it goes by the nickname "DAAB". Its a collection of > helper > > methods build around a static class called SqlHelper. There's close > to > > 50 methods like this: > > > > numRows = SqlHelper.ExecuteNonQuery(ConnectionString, > > CommandType.StoredProcedure, "UpdateNews", parameterArray) > > > > It has Execute* methods for DataReaders, DataSets, XmlReader(?), > etc. > > > > Here is the forum on www.asp.net: > > > > http://forums.asp.net/117/ShowForum.aspx > > > > I believe the first few versions only worked with SqlClient. Maybe > > they've expanded it to work with other databases. Its my > understading > > that the Application Blocks are written by Microsoft MVPs and not > by > > Microsoft. > > > > There are other blocks too. I've glanced at the Enterprise Library > > Logging Application Block but after seeing blog posts like this: > > > > http://weblogs.asp.net/lorenh/archive/2005/02/18/376191.aspx > > > > I like log4net even more. Last time I checked, the Enterprise > Library > > Logging Application block had a uber-complicated xml config that > could > > not be changed at run-time (i.e. you couldn't change from DEBUG to > INFO > > logging at run-time) and there was a seperate GUI just to generate > the > > xml config file that the program needed. I've heard other people > talk > > of stupid things like the severity of log messages being rated > > ascending but other parts of the system using a descending scale to > > indicate levels of severity. > > > > --- Brandon Goodin <[EMAIL PROTECTED]> wrote: > > > Does anyone know much about this project (Data Mapping > Application > > > Block)? > > > > > > The Data Mapping Application Block C#, VB.NET > > > > > > "The Data Mapper is a layer of software that separates the > in-memory > > > objects from the database. Its responsibility is to transfer data > > > between the two ends to isolate them from each other. With Data > > > Mapper > > > the in-memory objects needn't know even that there's a database > > > present; they need no SQL interface code, and certainly no > knowledge > > > of the database schema." (Fowler, Martin, Patterns of Enterprise > > > Application Architecture, p. 165) Data Mappers equate to what is > > > known > > > as Data Access Logic Components (DALCs). This application block > is > > > intended to make it easier for producers of business DALCs to > create > > > common functionality that relates to managing "entities" with > CRUD > > > functions. The DataMapper also promotes the use of stored > procedures > > > as a best practice to abstract data access from the underlying > data > > > schema and increase performance. Finally, the DataMapper allows > > > capabilities like the use of transactions, command timeouts, and > > > caching properties to be added, removed, and modified through > > > configuration when needed. For example, to add transactions or > > > caching > > > to a DALC, no code will need to be modified -- only configuration > > > settings. > > > > > > > > > http://www.gotdotnet.com/workspaces/directory.aspx?&Column=ActivityPercentile&Direction=DESC&Page=6&Size=10&FO=1&PPS=1 > > > > > > Brandon > > > > > >
