Remember that each project gets compiled to its own assembly. So, you can have just a handful of projects, each containing multiple .cs files.
>Thanks everyone, that helps a lot.
>
>I'm thinking I probably should avoid having 200+ DLLs in a project if I can avoid it.
>
>So I think I'll design some main DLLs for high use stuff like controls and datasets etc, then specialty type stuff that doesn't get used much can go into some other DLLs or be in stand alone DLLs.
>
>Another DLL or 2 that is specific to a group of apps (Handling data and forms/controls that are common to that set of apps.)
>
>A Main EXE and maybe a DLL or 2 directly related 2 it to keep some sense of order in the code, and I should be good to go.
>
>I like having at least some feel for the overall layout before I plunge in and start building stuff. I think I have that now.
>
>John
>
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer