Possible Duplicate:
Continuous Integration and Vb6 compilation
I am implementing Continuous Integration using Cruise control.net and have more than 50 legacy Vb6 .dlls. Some of .dlls are dependent on each other.
For ex: A.dll is dependent on B.dll. All .dlls are complied into one Common folder let say "Bin" and binary compatible. If signature of a method in B.dll is changed, vb6 IDE shows dialog box either to "Break Compatibly" Or "Preserve" it. If i select "Break Compatibly", it then shows a confirmation message to either to cancel or continue. If i say continue, then .dll gets complied. After that if i compile A.dll it gets compiled.
However, while compiling .dlls using code for Continuous Integration, i do set no-compatibility for B.dll then complied. After that when i compile A.dll i get error saying "Library Not found" for Classes in B.dll.
Want to know what is the problem here. Does Vb6 IDE set B.dll to NoCompatibilty when i say break? Otherwise, what are steps Vb6 IDE does in this scenario. How to handle this kind of scenarios?
Can anyone help me.
Regards, Chandan