Get The Data Mapper Application Block


If you were at our last webcast and saw the Data Mapping Application Block, Lenny has a preview ready for you now!  This block is frekin’ cool! Go get it here. [Lenny is writing a book for AW “Effective Use of Enterprise Library” (subject to change)] 

From the site:

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.


Now playing: Jimi Hendrix ExperienceHighway Chile

Comments (4)

  1. Just to ask the obvious and obnoxious question, in what way is this different or better than NHibernate or any of the other existing open source tools? Other than sproc’s or the fact it will be semi-supported by MS?

    I’m still aggravated at MS for the ObjectSpaces fiasco. I think it set back the .NET community quite a bit by putting a lid on persistence tools. It’d definitely be cool to see something from you guys on this.

  2. Jason Haley says:

    A few interesting finds

  3. ::Just to ask the obvious and obnoxious

    ::question, in what way is this different or

    ::better than NHibernate or any of the other

    ::existing open source tools?

    After a fast run through the features the difference is that it looks likea beginner prototype that should be thrown away, comparing it with real O/R mappers /(NHybernate, EntityBroker, LLBGEN Pro). It basically lacks nearly every feature that I consider the advantages of such tools (dynamic object based queries, db independant, caching, oo features) and is extremely basic and crude, when you compare it to them.

    Been there (at the site), seen, had a good laugh.