I look at this rather differently from apparently just about everyone else. If I need 6 people to work on a word document, I don't make one document. I make several. Industry experts like Steve McConnell tell us to make code small, discrete and modular. That's for when the module is operating at runtime.

I apply this concept at design time as well. I break the classes down into separate VCXs. That way each developer can have individual access to the class they're working with and can pack them at any time.

>Thanks you for the comments.
>
>I could open the page which displays the list of downloads, but the link to download the ZIP didn't work. Error: Page Not Found
>
>Anyway, The main idea was the important.
>
>
>
>Thanks.
>Juan C.
>
>
>>>Juan,
>>>
>>>Especially in classes where there is lots of containership, you get vcx bloat because the each object row gets deleted rather than reused. The best thing you can do to keep things under control is use a project hook to pack your classlibs prior to building.
>>>
>>>>My Cursor Adapter class library (VCX) size is about 2MB , and there are 6 developers at a time. Every time one of us builds the EXE, the class library is recompiled but it increases its size about 1-2 MB every time until I can use the .vcx file exclusive and perform the PACK.
>>>>
>>>>Is there any way to avoid this situation? Because the EXE file also increaes its size.
>>
>>Good Idea.
>>
>>Just to start with, I through this to gether.
>>
>>http://www.GLRsoftware.com/download.asp#ph_VCXpack.zip