Hi
I have a dll ('dll-X') which runs on top of (dependent upon) several
other dlls.
My build environment has a folder structure
binaries
compat-libs
so I put the target compatibilities into the compat-libs folder and then
I compile against those target libs and place the resulting binary into
the binaries folder.
The dll versions on which dll-X is dependent may well change their
public interface, but dll-X doesn't. It is always using the same source
code. I thought I should be able to rebuild with binary compatiblity,
but I can't. I set compatibility to project and it rebuilds okay. I can
then rebuild with binary compatibility.
I don't know what is stopping me building with binary compatibility and
am wondering how I can find this out. I have manully checked through the
registry looking for old references to the dll-X but can't find anything.
Further, it seems that any component which is dependent on dll-x can no
longer build with binary compatibility even if their public interface
doesn't change.
Now perhaps I've misunderstood binary/project compatibkity but I thought
if the interface remains the same, then I should be ablwe to compile
with binary compatiblity.
Could anyone correct my misunderstanding if I have one and if not, give
some pointers as to how I can track down what is causing VB not not
permit me to compile with binary compatibility
Many thanks
Simon
