'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix VSTO Runtime Compatibility Issues for Excel Add-ins
Question details
The user is experiencing compatibility issues where an Excel add-in built with Visual Studio 2019 requires VSTO 2010 Runtime in older Office versions but works without it in newer versions.
- Product
- Microsoft Excel
- Device & OS
- not provided
- Scenario
- Deploying a custom Excel add-in across different versions of Microsoft Office (2010, 2013, 2019, Microsoft 365).
- Observed behavior
- The add-in fails to run on Office 2010 and 2013 without manually installing the Visual Studio 2010 Tools for Office Runtime, but operates normally on Office 2019 and Microsoft 365.
Verify the exact versions of Microsoft Office installed on the target machines and ensure you have access to the add-in's original Visual Studio project files.
Verify Target Framework and Update Prerequisites in Visual Studio
Check your project's target framework and deployment prerequisites to ensure the necessary runtimes are automatically bundled for older Office versions.
Office 2019 and Microsoft 365 typically include the necessary VSTO runtime components built-in, whereas older versions like Office 2010 and 2013 require the runtime to be installed separately. By updating your deployment package, you can automate this process for end users.
Open your Excel add-in project in Visual Studio 2019. Right-click the project name in the Solution Explorer and select 'Properties'.
Navigate to the 'Application' tab and check the 'Target framework' dropdown to ensure it aligns with the requirements of your target Office versions.
Go to the 'Publish' tab and click on the 'Prerequisites' button.
Ensure the checkbox for 'Visual Studio 2010 Tools for Office Runtime' is selected. This forces the installer to download and install the runtime on client machines that lack it.
Consult the Microsoft Office Development Community
Seek specialized support from Microsoft engineers for complex VSTO runtime and deployment behaviors.
Try WPS Office for a Lightweight Spreadsheet Experience
While custom VSTO add-ins are specific to the Microsoft Office development environment, WPS Office offers a streamlined, highly compatible, and free alternative for everyday spreadsheet tasks. It natively supports standard Excel formats without the overhead of complex runtime dependencies.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the on-screen instructions to install the lightweight suite.
- 3. Open Your Spreadsheets: Launch WPS Spreadsheets and open your existing .xlsx files directly to enjoy a seamless, runtime-free experience.
Frequently Asked Questions
Why does my Excel add-in need VSTO 2010 Runtime on older Office versions?
Older versions like Office 2010 and 2013 do not always have the latest VSTO runtime embedded or updated by default. Installing the VSTO 2010 Runtime bridges the architecture gap between your modern Visual Studio code and the older Office application.
Can I run VSTO Excel add-ins in WPS Office?
No, VSTO (Visual Studio Tools for Office) is a proprietary Microsoft framework designed specifically for Microsoft Office architecture. WPS Office has its own add-in ecosystem and supports standard VBA, but it cannot execute Microsoft VSTO COM add-ins.
How do I include the VSTO runtime in my add-in installer?
In Visual Studio, right-click your project, go to Properties, select the Publish tab, and click Prerequisites. Check the box for 'Visual Studio 2010 Tools for Office Runtime' so it is bundled with your ClickOnce or Windows Installer package.
Does Microsoft 365 require a manual VSTO runtime installation?
Typically, no. Modern versions like Office 2019 and Microsoft 365 include the necessary VSTO runtime components out of the box, which is why your add-in works seamlessly on these platforms without requiring a separate download.
