>Bonnie, can you tell me why you see a problem in having base classes in different files? Serious question.
Mainly, I would think that it is easier to find your classes if they are somehow categorized. Combining them into classlibs is one way to do it. (Another might be separating them into directories.) But I would still hate to have a long list of classlibs listed in my project.
I was going to say "requires a long SET CLASSLIB", but I think that wouldn't really be required for base classes. For instance, for a TextBox (based on a cTextBox class) placed on a form, the classlib is stored together with the classname.
===========
Update: Sorry, I thought this was about Visual FoxPro. I am not sure if the same ideas apply to .NET.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
