M
Martin Krimpelstätter
I've written a COM add-in for Visio 2003 in VB.NET using the Visual Studio
..Net Extensibility Project Template. After building and installing the add-in
via the setup project generated automatically by the Extensibility Wizard the
add-in is loaded as intended when Visio starts. The OnConnection-method is
called and the add-in properly handles a MarkerEvent-event raised by the
QueueMarkerEvent add-on.
When I try to debug the add-in using Visual Studio, Visio is started but the
add-in isn't called. After I tried to debug the add-in, it is displayed as
deactivated in the COM add-ins dialog box in Visio and can't be activated
again. Visio only calls the add-in again after I have reinstalled the COM
add-in.
Does anyone have an idea how I can persuade Visio to call my add-in when
debugging and not to deactivate it? I have written a COM add-in for Word too,
and I've no difficulties when debugging it in Visual Studio.
..Net Extensibility Project Template. After building and installing the add-in
via the setup project generated automatically by the Extensibility Wizard the
add-in is loaded as intended when Visio starts. The OnConnection-method is
called and the add-in properly handles a MarkerEvent-event raised by the
QueueMarkerEvent add-on.
When I try to debug the add-in using Visual Studio, Visio is started but the
add-in isn't called. After I tried to debug the add-in, it is displayed as
deactivated in the COM add-ins dialog box in Visio and can't be activated
again. Visio only calls the add-in again after I have reinstalled the COM
add-in.
Does anyone have an idea how I can persuade Visio to call my add-in when
debugging and not to deactivate it? I have written a COM add-in for Word too,
and I've no difficulties when debugging it in Visual Studio.