BUG: Changing Implemented Class Does Not Give Compatibility Error (190967)
The information in this article applies to:
- Microsoft Visual Basic Professional Edition for Windows 5.0
- Microsoft Visual Basic Professional Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
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.
Modification Type: | Minor | Last Reviewed: | 1/8/2003 |
---|
Keywords: | kbbug KB190967 |
---|
|