Visual Studio debugging fails.

[Martin]

Hi all,

I used the "Visio Add-In" project type to build my own add-in. So
registry entries and all that stuff has already been generated.

If I try to run it in debug mode Visio starts and then crashes (without
any error).
So I gave it a second try. This time Visio asks me if I'd like to
disable my add-in because it had created the crash before. So it's
totally not possible to run the add-in from my Visual Studio (2003).

Now the strange stuff: If I run Visio separately there is no problem.
The add-in is loaded and the dummy message ("XY connected.") is shown.

So why does it crash if I use the "debug" button (F5) within Visual
Studio.
The workaround is fine. But if you are trying to test it's kind of
annoying


Thanks for your help in advance,
Martin

 

[Michel LAPLANE]

In some case when addin crash a special key is written in the registry under
HKCU\software\Microsoft\Office\11.0\Visio.
This key is "Resiliency". It contains the name of the addin that crash if
you reply yes to Visio when he ask you to deactivate a bugged addin for
ever. Visio look at this key at startup and did not launch any addin that is
contained in this key.

So look at HKCU\software\Microsoft\Office\11.0\Visio\Resiliency and delete
all his content. You can also delete the resiliency key.

 

[Pedro Silva]

Go To
Help --> About Microsoft Office Visio ---> Click on button named
"Disabled Items" to enable it again.