When working with lots of associated "supporting" classes alongside classes
(by this, I mean things such as associated component editor classes
specified by [Designer], debugger proxy classes specified by [DebuggerProxy]
etc. etc.), what kind of project structure do people use along with this?
Nested classes within the main class? (What I've used so far, but gets a bit
unwieldy in terms of file size once you have lots of such classes within a
class.)
Separate classes at the same level within the project? (Makes my eyes go
funny when I have ClassWithAVeryVeryVeryVeryLongName.cs,
ClassWithAVeryVeryVeryVeryLongNameDesigner.cs,
ClassWithAVeryVeryVeryVeryLongNameDebuggerProxy.cs etc. etc. all in a
project for lots of classes. At least with the nested classes approach you
can avoid this kind of thing.)
Per-class folders within the project keeping a single main class and all its
supporting classes together?
Folders within the project called Designers for all designer classes,
DebuggerProxies for all debugger proxy classes etc.?
Separate assemblies?
