How to automatically fix MISSING reference in a dll when a referenced library is broken in VB6?

What do you do when you break compatibility on a common library used by many other libraries on your development machine?

What I usually do is:

For every dll that reference the broken one
 Checkout dll
 Checkout vbp project
 Open vpb project with VB6 Ide
 Click on References button 
 Uncheck MISSING reference and OK
 Click on References button 
 Check references and OK
 Click on Make dll
 Cl开发者_C百科ose project

This can be a pita activity, when you have many Dll to recompile and it can be error prone because you could miss some Dll. I think this problem is more related to development machine; on our staging/production server we have build tools that fix the MISSING problem automatically.

What's your best practice to handle this common scenario on your local machine?

The Way We Work -- section Handle broken references is almost the way we work.

Here is a link to the tool by LJ Johnson -- Take Control of Your Build Cycle. We are using a custom build tools in our daily builds that reads separate REF files.

If you open the vbp with notepad then you should be able to update the reference without actually opening the project. Obviously you'll need to make sure you give it the correct CLSID.