Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Here are some questions for troubleshooting:</p> <ul> <li>What kind of add-in are you developing? A Shared Add-in or a VSTO? If VSTO which version?</li> <li>What OS are you using? Vista can be tricky...</li> <li><p>Check the LoadBehavior of your add-in in the Registry. You find the value either in</p> <pre><code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Word\Addins\&lt;add-in class name&gt;\ </code></pre> <p>or </p> <pre><code>HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Word\Addins\&lt;add-in classname&gt;\ </code></pre></li> </ul> <p>If the value of LoadBehavior is 2 your add-in has been disabled during startup. This happens when Word cannot instantiate the add-in, typically because the add-in throws an unhandled exception, or - much more often - because the add-in is not correctly registered.</p> <p>Have you checked that the VSTO runtime is correctly installed on the target system?</p> <p>However, even if you use VSTO, for Word the add-in still looks like a classic COM add-in which is extending the classic IDTExtensibility2 interface. Such add-ins must be registered the following way:</p> <ul> <li>One of the two registry keys above to tell Word the class name of the add-in plus additional information such as the load behavior and a description</li> <li><p>The class name of the add-in must be registered under</p> <pre><code>HKEY_CLASSES_ROOT\&lt;add-in classname&gt;\CSLID </code></pre></li> <li><p>The correct version of the COM component must be registered under (where {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} is the guid of the component as specified under HKEY_CLASSES_ROOT\\CSLID): </p> <pre><code>HKEY_CLASSES_ROOT\CLSID\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} </code></pre></li> </ul> <p>The following two links might also help you further narrowing down your problem:</p> <blockquote> <p><a href="http://www.mztools.com/articles/2007/MZ2007009.aspx" rel="nofollow noreferrer">HOWTO: Troubleshooting Visual Studio and Office add-ins</a></p> <p><a href="http://blogs.msdn.com/dvespa/archive/2008/10/15/troubleshooting-outlook-com-addins-using-procmon.aspx" rel="nofollow noreferrer">Troubleshooting Outlook COM Addins – Using ProcMon</a></p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload