Klaus Huebschle
April 13th, 2001, 06:12 AM
I have the following problem:
I have developped ActiveX Controls using Visual Basic 6.0 SP4.
I have an Visual C++ application which allows
dynamical creation of ActiveX controls.
No I want to debug these ActiveX Controls using VB source code debugging. The Controls shall be run inside of the Visual C++ Application.
I start the VB IDE, load the Control Project and Start Debug Mode with option "Wait for components to be created" selected.
Then I start my Application. The creation of the component fails with ErrorCode "0x80040154" (REGDB_E_CLASSNOTREG).
This means that the component is not registered
appropriate.
After having researched the problem I think that it is not posiible at all to debug an VB Usercontrol in VB if not using a second test project (in a project group) or in a HTML page.
If have tried to use an VB Standard EXE as host application. The effect is the same like in C++.
So it's no VB Problem.
This was the effect on Win2k.
On NT4 the behaviour is a little bit different. But it doesn't work, too.
Is this a general behaviour of VB ?
Has anybody done this before and it worked under certain circumstances ?
I have developped ActiveX Controls using Visual Basic 6.0 SP4.
I have an Visual C++ application which allows
dynamical creation of ActiveX controls.
No I want to debug these ActiveX Controls using VB source code debugging. The Controls shall be run inside of the Visual C++ Application.
I start the VB IDE, load the Control Project and Start Debug Mode with option "Wait for components to be created" selected.
Then I start my Application. The creation of the component fails with ErrorCode "0x80040154" (REGDB_E_CLASSNOTREG).
This means that the component is not registered
appropriate.
After having researched the problem I think that it is not posiible at all to debug an VB Usercontrol in VB if not using a second test project (in a project group) or in a HTML page.
If have tried to use an VB Standard EXE as host application. The effect is the same like in C++.
So it's no VB Problem.
This was the effect on Win2k.
On NT4 the behaviour is a little bit different. But it doesn't work, too.
Is this a general behaviour of VB ?
Has anybody done this before and it worked under certain circumstances ?