How can you force VB6 to use the DLLs and OCXs from the app directory?

Question

I want to put my dependent files in the app directory.

I seem to remember that you can force VB6 to use the files in the local directory only.

Any hints?

Answer 1

Placing component libraries in the EXE folder (with or without .local files) can be deleterious to the hygiene of target machines too.

VB6 programs will register the components here via the self-reg entrypoint behind your back if they are not previously registered. Then if the application is moved or removed you leave the user with a broken reigistration - possibly fatal to subsequently installed applications using some of the same components. This is probably fine though for application specific components, i.e. your own DLL or OCX that will never be needed by another application.

The .local trick was really not meant for use with VB6 programs and if it is used your installer needs to be aware and properly install and register the components if they are not already on the machine. It was meant as a manual hack to get around DLL version compatibility problems on individual machines, not a deployment strategy.

Move up to SxS application and assembly manifests (Reg-Free COM and more) for a better solution. DLL/COM Redirection (.local) was a good try but it has many warts.