It can be done... somehow. :) Lets say you have a level A of classes that you want to hide and a level B (subclassed from A) that you want to give to the user. You need a level C between A and B. In all classes on level C, make the Parent and ParentClass properties private/protected. There are also some methods that must be hidden (Like SaveAsClass).

Of course, you must include A and C into APP/EXE and build encrypted. B must be included and excluded (! :)).

HTH,
Vlad

>i was hoping i could set the project so you couldn't see what the parent classes are. can't be done. we have programmers who will make changes to these without permission (and without documenting them). i'd like to hide this info from them, but....
>
>
>>Why "not quite"? ...I think you don't want to distribute the parent classes at all, neither in nor outside your APP/EXE... :)
>>
>>Vlad
>>
>>>not quite, but the best idea so far. thanks.
>>>
>>>>Include them into project, go to Project menu and choose Exclude. In this way, the project manager won't complain and the VCXs won't be included in the APP/EXE.
>>>>
>>>>Hope this is what you want. :)
>>>>
>>>>Vlad
>>>>
>>>>>this is just to much for a friday morning. we have subclassed several class libraries and would like to use these in a project. our problem is that we don't want the parent classes included, but the project manager always includes them. how (can) you avoid this?