Article ID: 169304
Article Last Modified on 11/18/2003
APPLIES TO
- 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 Q169304
SYMPTOMS
Errors occur when getting property of a Visual Basic Project and the program crashes. The random nature of this reproducible scenario is due to the fact that the add-ins are loaded in random order. This behavior may not be reproducible if the source code control add-in is listed before the repository's add-in.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed At the beginning of this article. This has been fixed with Visual Studio Service Pack 1.
For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why
MORE INFORMATION
The Order of Source code control and Repository is important in the event chain.
Steps to reproduce:
- Edit the VBADDIN.INI and add the following line: Repository.VBAddin=1.
- Run Visual Basic 5.0. In the Tools and Add-Ins menus, verify that Visual SourceSafe and Repository have been loaded.
- Open one of the sample projects, such as: "\samples\entrpris\hello\Helo_cli.vbp."
- When prompted with "add this project to SourceSafe," answer Yes. Log on and make sure all files are selected to be added to Visual SourceSafe.
Result:
After you press OK on the error dialog box, Visual Basic also shuts down.
If you re-run Visual Basic and try to re-load the same project, Visual Basic will ask if you want to get the latest version of the files from Visual SourceSafe. If you answer Yes, the same error occurs and Visual Basic shuts down again.
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp1fix kbvs97sp2fix kbvbp500sp1fix KB169304
