Also, if you're working in a team environment it can become very difficult to work on an application if all the classes are in one VCX.

>IMHO, it is better to spread your class defintions over multiple VCX's with some logical grouping in the VCX. Why? What if you have a different project, but only need a few classes from this project. If you place your classes in one VCX, you will drag everything over to the new project. Also, when VCX's get large, performance in instancing classes degrades.
>
>HTH