Article ID: 190080
Article Last Modified on 3/3/2005
APPLIES TO
- Microsoft Visual Basic 6.0 Learning Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual Basic 6.0 Enterprise Edition
- Microsoft Windows CE Toolkit for Visual Basic 5.0
This article was previously published under Q190080
SYMPTOMS
Attempting to debug an Add-In project built in Visual Basic 6.0 while having the Windows CE Toolkit for Visual Basic 5.0 (VBCE5) installed on the system and loaded within the Add-In Manager Dialog for Visual Basic 5.0 leads to an Application Error.
RESOLUTION
Deselecting the Windows CE Add-In from the Visual Basic 5.0 Add-In manager prevents further Application Errors.
STATUS
Windows CE Toolkit for Visual Basic 5.0 is not intended to work with Visual Basic 6.0.
MORE INFORMATION
Steps to Reproduce Behavior
The steps below assume Visual Basic 5.0 and 6.0 are both installed on the system, as well as the Windows CE Toolkit for Visual Basic 5.0.
- Start Visual Basic 6.0 and create a new AddIn Project, with its default name of "MyAddIn."
- Press the F5 key to run MyAddIn.
- Run a second instance of Visual Basic 6.0. The following error message appears:
- Click No.
- Create a New Standard EXE project, Project1. Form1 is created by default.
- Close Project1 without saving and open a New ActiveX DLL project. The ceide dialog box appears with the following text:
- Click OK, and note that the ActiveX DLL project is loaded.
- Close the instance of Visual Basic 6.0 that is not running the Addin project and note that an Application Error occurs.
Additional query words: vbce vbce5 wince wce
Keywords: kbide kbtoolkit kbaddin kbprb KB190080
