By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,639 Members | 2,000 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,639 IT Pros & Developers. It's quick & easy.

"Supporting" classes and project structure

P: n/a
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?
Aug 27 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.