I try to make VCX the smallest possible by regrouping only related classes in it. Like you experienced, as soon as you reference one class inside the VCX, the whole VCX get included in your project, making it not only bigger, but also longer to compile. IMHO, you just definitly try to break up this VCX into smaller pieces.

>And my doubts are about how to make the visual class architecture. This visual class architecture should be used for many app projects. The main point is to padronize the user interfaces.
>
>I'm creating my visual class in just one vcx: "visual.vcx". This vcx is about 3.5Mb.
>I'm developping an app that uses almost only 10% of this vcx. And my project that can be with a few kbs, have 4Mb.
>
>My asks comes here: Is my "visual.vcx" in a bad architecture? Do any of you project visual class on two or more vcx? Anybody has a problem with it?