BUG: Changing Implemented Class Does Not Give Compatibility Error
Article ID: 190967
Article Last Modified on 1/8/2003
APPLIES TO
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
This article was previously published under Q190967
SYMPTOMS
If a Visual Basic Class implements an interface of a referenced dll, then
the implemented dll is removed and replaced with a different dll which
contains the same interface names as the first reference, an
incompatibility error is not generated when recompiling the dll with Binary
Compatibility set.
For example, if Project1.dll implements Class1 in MyFirst.dll, then the
reference to MyFirst.dll is removed and replaced with a reference to
MySecond.dll (which also contains a Class1), recompiling Project1 does not
generate a compatibility error.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products
listed at the beginning of this article. We are researching this
bug and will post new information here in the Microsoft Knowledge
Base as it becomes available.
Additional query words: kbDSupport kbVBp600bug kbVBp500bug kbCompiler kbdss kbDSupport kbVBp
Keywords: kbbug KB190967