will this Design work?

[shan chennai]

hi...

i have a design as follows...

Presentation Layer (.aspx, .cs) -- Service Layer (just a facade) --
Business Layer (business objects) -- Data Layer (all DB related things
for business objects are done here) -- Data Access Application Blocks
-- DataBase

No we pass objects and not datasets across layers ..

Typically the flow is ...

_ Click --> ...-->.. the business objects are populated using
DataReader.. the collection of Business Objects are returned (collection
is a strongly typed collection for the business objects ) ...at the
presentation layer (service facade),the business objects are converted
to VIEW Objects ( views are typically a wrapper over the business
objects which expsose some properties of business objects for view
purpose--typically to bind data) ... the view objects are put into a
viewCollection (again a strongly typed colletion) and then BOUND TO THE
DATAGRID etc...

NOW CAN YOU PLEASE TELL ME IF THERE is any flaw or disadvantage here
other than the extra code we need to write and unavailability of rich
features of dataset ???

can you forsee any problem with such a design..

it actually helps me to use Object oriented design concepts and
patterns...


Please give ur comments...

 

[Nicholas Paldino [.NET/C# MVP]]

Shan,

Well, the biggest issue is the fact you have to write all of this. I'm
not saying that data sets are better or worse for what you want to do, but
the immediate drawback is that you will have to write code for all of the
functionality that you lose with DataSets.

Hope this helps.

 

[xAvailx]

The following frameworks may be of help to you:

http://www.lhotka.net/
http://cstemplates.sourceforge.net/

hth