Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Cannot debug or run Word AddIn because the required version of Microsoft Office is not installed

I need to work on an existing Word 2007 addIn project that's a part of a MSVS 2008 solution. However, when I try to debug the addIn, I get the following error message: "You cannot debug or run this project, because the required version of the Microsoft Office application is not installed". I have Office 2007 installed.

I tried creating a new Word 2007 addIn project in the same solution, and I have no problem debugging it. As far as I can tell, all the referenced Office assemblies are the same between these two projects.

Referenced Office assemblies:

Microsoft.Office.Interop.Word (c:\Program Files (x86)\Microsoft Visual Studio 9.0\Visual Studio Tools for Office\PIA\Office12\Microsoft.Office.Interop.Word.dll)

Microsoft.Office.Tools.Common.v9.0 (c:\Program Files (x86)\Reference Assemblies\Microsoft\VSTO\v9.0\Microsoft.Office.Tools.Common.v9.0.dll)

Microsoft.Office.Tools.v9.0 (c:\Program Files (x86)\Reference Assemblies\Microsoft\VSTO\v9.0\Microsoft.Office.Tools.v9.0.dll)

Microsoft.Office.Tools.Word.v9.0 (c:\Program Files (x86)\Reference Assemblies\Microsoft\VSTO\v9.0\Microsoft.Office.Tools.Word.v9.0.dll)

Office (c:\Program Files (x86)\Microsoft Visual Studio 9.0\Visual Studio Tools for Office\PIA\Office12\Office.dll)

stdole c:\Program Files (x86)\Microsoft Visual Studio 9.0\Visual Studio Tools for Office\PIA\Office11\stdole.dll

I tried rebuilding, starting debug under both Debug and Release configurations. Nothing helps. What else am I missing that could cause a problem with debugging the old project?

like image 298
sdds Avatar asked Aug 15 '13 10:08

sdds


People also ask

Why can't I add add-ins on word?

Check if Templafy add-ins are enabled in an Office application. If the add-in is not enabled, please do so by clicking on the checkbox. Check if load behavior is set to Load at startup. Additional Slideproof troubleshooting.


2 Answers

Apparently, when the addin project is created, debug information such as the MS Office version and the executable path used for debugging is saved in the .CSPROJ file.

So debug is not guaranteed to work on another machine.

This information is saved in following XML node of the project file:

ProjectExtensions \ VisualStudio \ FlavorProperties \ ProjectProperties

In my case, the problem was in the attributes

  • OfficeVersion="14.0"
  • DebugInfoExeName="#Software\Microsoft\Office\14.0\Word\InstallRoot\Path#WINWORD.EXE"

Changing 14.0 to 12.0 (2010 to 2007) in their values solved my problem.

Check out these questions for reference:

  • Determine Excel 2007 addin vs excel 2010 addin
  • convert an Excel 2010 addin to a 2007 addin (both VSTO)
like image 129
sdds Avatar answered Oct 01 '22 03:10

sdds


For the benefit of searchers, I hit this error in Visual Studio despite referencing the correct version in the section mentioned by @sdds.

For me the fix was:

  1. Go to the project properties in visual studio
  2. Go to the 'Debug' tab
  3. Click the 'Start External Program' radiobutton
  4. Enter the path to the Office Application e.g. C:\Program Files\Microsoft Office 15\root\office15\winword.exe
  5. Run the project.
like image 24
JsAndDotNet Avatar answered Oct 01 '22 04:10

JsAndDotNet