Colin,

Aside from the other good ideas you have recieved you do have one fairly simple approach for the old apps.

Say your old VCX is MyLib.Vcx. You split that into a number of libraries non of which use MyLib.Vcx. Now you no longer need MyLib.vcx. Ok, for your old apps, replace the old MyLib.vcx with a new one which simply subclasses all the objects from the new libraries. Your old apps look to MyLib to find the objects and they are there so everything *should* work. What are the problems with this approach? The biggest is dependand on how you call default methods in the superclass. If you use :: notation, then you may find that have some problem. If instead you use the DODefault() funtion, you should be fine.

One other advantage to this approach is that if you have added a new feature that you don't want exposed to the older apps, you can override that feature in MyLib.

Just one more way to solve the problem.

Fletcher


>I'll look into it. Thanks for the advice.
>
>>Maybe the VCXEditor of Rock Legendre could help you to do this.
>>
>>>I have a class library that I've used for quite a few apps. Over time, as I created new classes or aquired them from resources like UT, I added them to this library. Now I want to split these classes into logical groupings in separate class libraries. Creating the new class libraries and moving the classes around is easy. What I need to know is what is the best (and hopefully easiest) way to update all my old apps to use the new class libraries? TIA