Cause: You installed the x86 VSTO runtime but Office is 64-bit.
Solution: Uninstall the x86 runtime and install the x64 version.
The x64 VSTO Runtime requires:
If you are deploying a VSTO add-in via ClickOnce, you can include the VSTO runtime as a prerequisite in your setup project.
You are most likely to encounter this runtime when:
$userVsto = "$env:USERPROFILE\AppData\Local\Apps\2.0" if (Test-Path $userVsto) Write-Host "User VSTO add-ins folder: $userVsto" else Write-Host "No user-installed ClickOnce VSTO add-ins found." microsoft visual studio 2010 tools for office runtime -x64-
Description
Why it helps
Key capabilities
Backward-compatibility and security
Developer benefits
Basic command-line examples
If you want, I can draft a short proposal or mockup UI text and command-line help for this feature.
[Invoking RelatedSearchTerms for further refinement] Cause: You installed the x86 VSTO runtime but
Here’s a useful feature you can prepare for the Microsoft Visual Studio 2010 Tools for Office Runtime (x64) — especially useful when deploying Office add-ins or maintaining legacy solutions.
For an x64 VSTO add-in to function, the target machine requires:
A frequent cause of mysterious add-in failures is a hybrid environment:
Run an x64 Office application (e.g., Excel 64-bit). Then open Event Viewer → Windows Logs → Application. Filter for source VSTO 4.0 . Successful loading produces an informational event: If you are deploying a VSTO add-in via
"The managed add-in [YourAddIn] was loaded successfully into the host process EXCEL.EXE (64-bit)."