One class per file rule in .NET?
- by Joan Venge
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?