.NET Guidelines: Should I have one class per file?

I had this discussion many times over the last few years:

• Should we have a class per file?
• What about other types such as interfaces, enums, …?

Opinions on this subject vary a lot. This purpose of this article is to provide you some basic guidelines and why you should follow them.

Table of contents

• General guidelines
• Advantages of having one type per file
  • Source Control
  • Finding Types
• Exceptions
• References