How to debug a VB6 ActiveX Control (OCX) using an External ActiveX Container (3rd party exe)

I've inherited several VB6 ActiveX controls which I need to debug.  I have the source code to the activeX controls.  The ActiveX controls run inside a 3rd party test container which I don't have the source code.  I've tried to setup the VB6 activeX project to 'Create Symbolic Debug Info' and the Version Compaitiblity is set to 'Binary Compatibility' and I have the 'When this project starts' set to 'Start Program: 3rdPartyExternalContainer.exe'

When I run the VB6 in debug mode it launches the 3rd party external container correctly.  I try to insert my activex control into the container but I don't see the appropriate behavior.  I'm expecting my control to show up with all the buttons, etc. but all I see is an outline of the control (black border) which tells me that it isn't working properly.

I noticed that when I lauch the ActiveX control from VB it will change my registry setting for InprocServer32 from my .ocx file to VB6Debug.DLL.  I'm not sure how the External container is suppose to know how to use this file versus my .ocx.

Is it possible to debug a VB6 activex control (.ocx) using a 3rd party executable container from within VB6?

Thanks,

--GSH
thehow11Asked:
Who is Participating?
 
Martin LissOlder than dirtCommented:
I doubt very much that you can do that since VB needs to be in control in order to do the debugging. Can you create a VB container that simulates what the 3rd party container does? BTW, what is the 3rd party container?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.