Microsoft KB Archive/171519
Article ID: 171519
Article Last Modified on 12/10/2003
- Microsoft Visual Basic 5.0 Control Creation Edition
- Microsoft Visual Basic 5.0 Learning Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q171519
If you recompile an ActiveX DLL with binary compatibility after changing the interface, Visual Basic will not always warn you. However, this action will result in an incompatible interface.
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.
For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why
For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2
Changing the interface to an ActiveX DLL (such as changing the arguments in a function or removing a function) should result in Visual Basic warning you of the change when you try to compile the new DLL. However, this may not happen.
Steps to Reproduce Behavior
- Start a new ActiveX DLL in Visual Basic 5.0.
Cut and paste the following code to the Class1 Class Module:
Public Enum Test Larry Curly Moe End Enum Public Sub Test() ' This comment is so this sub compiles End Sub
- Under the Project | Project Properties | Component menu, make sure the project's version compatibility is set to "Project Compatibility." (It should default to this setting.)
- Compile Project1.DLL.
- Comment out the Test Sub.
- Under the Projects | Properties | Component menu, switch the projects version compatibility to "Binary Compatibility." Make sure the compatible version file is Project1. (This is the default setting.)
- Compile Project1 again. This time, save the filename as Project2. Visual Basic will compile the DLL without any complaints although it should raise a 'broken compatibility' warning dialog box.
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171519