ActiveX DLL - Best Practices
Posted on 2003-03-14
I have an activex dll that performs internet functions and use it in many projects (internet.dll)
I create many custom activex dlls for different projects and include a reference to this (internet.dll) within that dll.
Whenever I need to make a change to (internet.dll), my references inside my other activex dlls that reference it get "screwed" up. I have to edit each one, and recompile. This is a headache!!!
1) Is it because the functions change and that breaks the binary or project compatablity, thus giving the dll a new guid?
2) Is it not good practice to have one activex dll reference another activex dll?
3) What is the best way to accompish this so that I don't lose compatiblity and have to recompile all these activex dlls all the time?
I will award the points to the person who can answer each question in detail and what might be the best practice and standard.