Objects

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

Guest

Hi,

I was wondering in your asp.net apps and this is outside of putting Web
and user controls on pages, do you guys build alot of objects in your app?
Meaning if you create an Employee object that uses collection, I would
consider this to be one. I guess what i'm getting at how many objects is to
much for an asp.net app and whats the average number of objects created for
an asp.net app? Also how many pages on average is your asp.net apps?

How do you monitor or gauge the performance of your app?

Thanks,

JJ
 
I guess what i'm getting at how many objects is to
much for an asp.net app and whats the average number of objects
created for an asp.net app? Also how many pages on average is your
asp.net apps?
Click to expand...

Your questions are meaningless as everyone's applications are of different
size.


Whether or not to create an object is a much more complex question... it
really depends on your application and the type of data you're
processing/using.
 
It depends what type of model you adopt. Table driven, entity drive, domain
driven, ... Personally, I'm of the opinion that entity driven is generally
the way to go (though there are so many cases where it might not be adequate
that I wouldn't even call them exceptions). In such a situation you'll
typically have entity classes which map to database tables, collections for
said classes, possibly utility classes for them. Of course these are only
objects which represent your entities. You'll also have classes as
HttpModules, each page you create is 2 classes (as is each user control).
You'll likely have a DAL, providers, ....

Karl
 
Back
Top