There are reasons and exceptions to every rule...and good reasons for doing so. But, pretty much everything I've seen shows one class per file.

>Another opinion ... I disagree on the "one class per .cs file" ... sorry Craig. I just don't think that should be a hard and fast rule by any means.
>
>We have a Controls.cs file that contains our base classes for a whole slew of controls. Things like TextBox, ComboBox, ListBox, ListView, etc.etc.etc. These sub-classes cannot be visually designed anyway, so putting a bunch of them all into one .cs file makes a lot of sense. I can't imagine having a MyTextBox.cs, MyComboBox.cs, MyListView.cs, etc.etc.etc. What a load of unnecessary files THAT would be! =0(
>
>Just my 2cents.
>
>~~Bonnie
>