One class per file rule in .NET?
Posted
by Joan Venge
on Stack Overflow
See other posts from Stack Overflow
or by Joan Venge
Published on 2010-03-12T18:45:33Z
Indexed on
2010/03/12
18:47 UTC
Read the original article
Hit count: 213
I follow this rule but some of my colleagues disagree with it and argue that if a class is smaller it can be left in the same file with other class(es).
Another argument I hear all the time is "Even Microsoft don't do this, so why should we?"
What's the general consensus on this? Are there cases where this should be avoided?
© Stack Overflow or respective owner