Bonnie,

Would the number of files be a problem - provided one keeps a folder/subfolder struct to group them ?
I can even imagine splitting one class into several files - keeping related methods/properties together

Is putting a lot of classes into one file any better ?

I wonder whether there's one answer to this question



>Pete,
>
>I know that you probably did this because it's been recommended (by me and others) to put all these non-visually-designable classes into one file. But, I'm wondering why you now want to separate them each into their own separate files? That will be quite a large number of files. It's really quite alright to leave them in one file.
>
>~~Bonnie
>
>
>
>>Hi All, I currently have all of the common .NET control classes defined in one ( getting bigger by the day ) file and am thinking of separating them into individual .cs's - does anyone know of a tool on the market that does this ? has anyone here written such a thing ?