Streamlining "DeepData"

tsaltd posted on Saturday, September 15, 2007

What's the "best practice" for new systems based on the DeepData pattern ( primarily to take advantage of moving the DataPortal_XYZ functions out of my BOs to a separate DAL assembly -- tho the child grandchild fetch pattern is also excellent )

I don't see why I would ever use anything but FetchDTO ... (I'm using an ORM tool that eliminates all ADO.NET code )

After stepping thru the debugger, I think I've got a handle on all the necessary functions that need to be migrated to my new app ( I'm also moving it from VB to C# ).

Of course I don't want to re-invent the wheel ... but I haven't seen anything that focuses on the modular DAL / DeepData functionality ... or a C# version ...

Is there any exisiting support for what I'm trying to do ???

 ???  Any gotcha's on moving away from the "dynamic" DAL functionality ??

Thanks,

Steve 

 

tsaltd replied on Monday, September 17, 2007

• No calls to app.config for "flexible DAL Libraries"  I'm putting constants in the DataFactory.GetYourNewXYZDataObject()

Type dalType = Type.GetType("MyNew.DAL.DTO.TransportData,YourNew.DAL.DTO", true, true);

• No ADO in the Business Objects ...only using DAL.DTO library with calls to ORM code in the DAL.DTO constructors

I'm not abandoning the possiblity of a different type of DAL library ... so I am sticking with implementing the IDisposable interfaces in MyNew.Dal for the MyNewDal.DTO.

Just scratching the surface .. but things are moving along.

Steve