Many classes vs Many methods in a single class, which is a better way to
structure applications?

Regards
James

James <arl***@hotmail.com> wrote:
Well, I generally favour small classes over large ones, but it really
depends on what you're doing. Sometimes a class just naturally ends up
large - and sometimes you end up with some very small ones which are
still perfect for the job.

Hello James,

There is a wrong approach to assess the size based on numbers of methods/classes.
You need to assess it based on the logic, and don't mess all in one. Each
class needs to mean smth specific and be self described
with the names of class and methods.

I found small classes with small methods is the best approach, it gives you
decoupling of system, clear understanding and team development flexibility


J> Many classes vs Many methods in a single class, which is a better way
J> to structure applications?
J>
J> Regards
J> James
---
WBR,
Michael  Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

Not creating an instance
How to make unique name given string and collection?
System.Boolean Question.
How to initialize jagged array?
ComboBox doesn't have border when appearance is made flat in VS.NET 2005
Can't debug unless copylocal=true?
decrease for
Image render and save problem
decreasing for
passing forms