Debugging VBVSL fails

K

Kari Yli-Kuha

We've implemented a VBVSL using basically Graham's VBVSL_Minimal example.

Environment:
- Windows 2000 SP4
- Visual Basic 6.0 SP5
- Visio 2002 and 2003

Symptoms:
Everything works fine in the run time environment - the DLL addon gets launched
from the document's static event list.
But - when I start debugging the code (start the addon and wait for Visio to initialize it)
all I get are two attempts to init the VBVSL class - the code never gets properly started.
The symptoms are the same in both Visio versions (2002/2003)

The funny thing is that the debugging used to work - and it still does with my
colleague. The only difference in our environments is that he's got W2K SP3 and
I upgraded to SP4.

Anyone got a clue?

/Kari
 
K

Kari Yli-Kuha

Kari Yli-Kuha said:
We've implemented a VBVSL using basically Graham's VBVSL_Minimal example.

Environment:
- Windows 2000 SP4
- Visual Basic 6.0 SP5
- Visio 2002 and 2003

Symptoms:
Everything works fine in the run time environment - the DLL addon gets launched
from the document's static event list.
But - when I start debugging the code (start the addon and wait for Visio to initialize it)
all I get are two attempts to init the VBVSL class - the code never gets properly started.
The symptoms are the same in both Visio versions (2002/2003)

The funny thing is that the debugging used to work - and it still does with my
colleague. The only difference in our environments is that he's got W2K SP3 and
I upgraded to SP4.

Further information: I installed the debug version of VBVSL_Min.vsl and started
the addon. This is what I got when debugging the code:

debugging:
1: Error: COM couldn't create VBVSL_MIN.VBVSL. Interface not supported
2: Created VBVSL Adapter Callback object
3: Registering addon: VBVSL_MIN_Adapter with index: 65535
4: Error: COM couldn't create VBVSL_MIN.VBVSL. Interface not supported
5: Trace opened from Visio
6: Error: COM couldn't create VBVSL_MIN.VBVSL. Interface not supported

whereas at runtime:
1: Created VBVSL Adapter Callback object
2: Load VB VSL, Result = 0
3: Registering addon: VBVSL_MIN_Adapter with index: 65535
4: Registering addon: VBVSL_Minimal_AddOn with index: 1
5: Trace opened from Visio

and everything works.

Next I'll install the windows symbol packages (.dbg) files and see if that helps.
For some reason they're not included in the W2K SP4 package.

/C
 
K

Kari Yli-Kuha

Forget this...

Recreating VB project (.vbp) from scratch after W2K SP4 installation solved the problem.

/Kari
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top