I have set "VSTO_SUPPRESSDISPLAYALERTS" environment variable to 0, and VSTO_LOGALERTS to 1 but
The output window shows that referenced files are loaded for my test add-in but not for this specific add-in. The reg key for HKEY_CURRENT_USER\Software\Microsoft\Office\Word\Addinsĭoes not list it.
After running debug, it is not listed as an active or inactive add-in, and there are no disabled items. The add-in should be loading when I run 'debug' from VS2013.
Which template you used to create VSTO before, with VSTO 2010 template or VSTOĢ007 template? When you test with VS2010, I think you need to install Office 2007 or Office 2010. But based on your description, it seems you both use Office 2013.
This error usually occurred when add-in template Office version is different from Office version you installed. > It is now saying "you cannot debug or run this project because the required version of Microsoft office is not installed Open Word Options dialog (File->Options) and navigate to Add-Ins tab, check whether yourĪdd-in is list in Disabled applicaiton add-ins. And then I suggest you check whether your add-in is disabled. With my above link, I suggest you check whether your add-in is installed correctly and it is enabled. 1000 32-bit and the VS2010 machine has Word. Required version of Microsoft office is not installed".
I have managed to re-open an old version in VS2010 (from a manual backup of the component that was not able to load) and get it running, but it is also not loading in word. It is now saying "you cannot debug or run this project because the
It has no build errors but has a code analysis error of the type CA0001 member "xx" could not be found in type "yy" I used Visual Studio 2013 to convert the solution and then fixed various problems to get rid of errors etc. >How did you port it to VS2013? If you open it in VS2010, will it work? This runs every time I debug - ie it displays the msg, it shows as a COM add-in, and it allows breakpoints to be hit. I created a new add-in which pinged a server and displayed a message. >Do you mean it worked correctly with a new add-in in VS2013? The code breakpoints are marked as never going to be hit "no symbols loaded for this document". >How do you check whether the add-in is loaded or not? Thanks for helping make community forums a great place. We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. How did you port it to VS2013? If you open it in VS2010, will it work? For Office addin does not load, I suggest you check the link below for a try. > I then (last year) ported it to a different machine running VS2013, and thought it was working >I have created a dummy test add-in in VS2013 which displays a message proving that it loads correctly.ĭo you mean it worked correctly with a new add-in in VS2013? If it is not checked, I suggest you check it to see whether this How do you check whether the add-in is loaded or not? After you launch your VSTO project, I suggest you check whether your add-in is list in Add-ins->COM ADD-INS, and whether it is checked. I'm beginning to feel there is some lost registry-value set the interferes with the Addin or that some files are missing.> BUT if I debug then the add-in does not load What we also has discovered is that when we try to activate the AddIn in Word UI, a new registry key is created in the Current_User-part of the registry with a singel value for Loadbehavior set to 2. We can see that no code in our Addin is executed because no entries in our logfile is found. We open the dialog for COM-Addins and when we try to fill in the checkbox, information is shown in the dialog that the AddIn is not lodaed and the reason is a runtime error. We look in the Word configuration - Addins, and our AddIn is amongs the inactivated ones. When we start Word we can se that an attempt is made to start the AddIn, but when the UI is shown, our menu is missing. When we look in the registry HKLM we can see that the Addin has Loadbehavior 3 as it should.Īll files from the package are in place and nothing seems to be missing. The Addins are all registered in the Local_Machine-part of the registry. In our investigation we have tried reinstall Office and also our package, but without success. The AddIns for Excel, Powerpoint and Outlook all works. We have a package of Office Addins for Word, Excel, Powerpoint and Outlook, all for Microsoft Office 2010.Ī couple of clients out of +500 has been getting problems starting/loading the AddIn for Word.