Visio 2003 Addon..

[James]

Hi,

I have developed a Visio Addon which is a vsl file which has been working
when the addon was installed in the visio application's addon path.. the
drawback of this is having to deal with the annoying security warning
prompting you to enable macro's. I have sinced removed the addon path from
the visio application settings and created a msi installation package and
published the addon component..

The addon appears to work fine, until you perform a shapesheet action using
the RUNADDONWARGS. I have debugged my addon, and i have noticed that Visio
isnt calling the addon to handle the commandline arguments. but visio is
managing to send events to the addon instead!?

Would anyone have any ideas why RUNADDONWARGS is failing to trigger my
addon? I suspect visio doesnt know the location of the addon to pass the
commandline arguments.. but why would this be, if the addon is now a
published component?

Regards
James

 

[James]

Sorted, managed to fix the problem myself!

Cheers

 

[Paul Herber]

Could you tell us how so that anyone finding this article in the
future can benefit ?

 

[James]

Sorry, I was rather frustrated due to the lack of visio sdk documentation.
With the rant put aside, it was obvious Visio was failing to call the addon
with the commandline arguments, and spotted one of the RUNADDONWARGS
parameter's didnt match the name of the addon.

Simple as that.