Explicitly build classes or use Dataset for everything...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hey all, I have a question regarding a very big design decision I am facing.

I am building an asp.net app with many classes for objects mimicking the
database design. It gets more and more cumbersome to manage the code each
time I add a new class. However, it provides me more flexibility to handle
each object more appropriately, as some objects differ greatly in their
required logic. Is it better to use a base wrapper class inheriting Dataset?
Are there any logical limitations or performance considerations?

Any help would be greatly appreciated!
 
A Database is just a storage for any kind of data. So, the first thing you
need to determine (or at least tell us) is, what are the business
requirements for this application? What is it used for? What is supposed to
do? The design of an application is always based upon business requirements.

--
HTH,

Kevin Spencer
Microsoft MVP
Professional Numbskull

If the truth hurts, wear it.
 
Welcome to the religious war :)

If your objects are tending to be very thin (i.e. not alot of domain logic),
you might want to consider taking a look at the ActiveRecord pattern. There
are numerous generators that can generate these objects for you either at
runtime or at compile time. This should help alleviate some of your woes :)

Cheers,

Greg Young
MVP - C#
 
Back
Top