Microsoft visual studio tools for office runtime is not installed

NET Framework. The Visual Studio Tools for Office runtime includes language packs. If your installation of Windows is set to a language other than English, you can display runtime messages in the same language that you use for Windows. Similarly, if end users install the Visual Studio Tools for Office runtime and then run your solutions on installations of Windows that are set to a language other than English, runtime messages will appear in the same language as Windows.

In some cases, you might need additional language packs. For example, you might need additional language packs if your copy of Windows uses more than one language setting, or you switch to another language after you've already installed the Visual Studio Tools for Office runtime. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful?

Privacy policy. This discussion includes steps for deploying a simple Office Add-in. ClickOnce can easily be used to create setups for your Add-ins and solutions.

However, it can't install Add-ins that require administrative privileges such as machine level Add-ins. Add-ins that require administrative privileges can be installed by using Windows Installer but it does require more effort to create the setup.

ClickOnce and Windows Installer packages need to do the same rudimentary tasks when installing an Office solution. Microsoft Office uses registry entries to locate and load Add-ins.

These registry entries should be created as part of the deployment process. Outlook Add-ins that display custom form regions require additional registry entries that allow the form regions to be identified. For more information about registry entries, see Registry entries for Outlook form regions.

Document-level solutions don't require any registry entries. Instead, properties inside the document are used to locate the customization. For more information about these properties, see Custom Document Properties Overview. In order for a customization to run, a solution must be trusted by the machine. The Add-in can be trusted by signing the manifest with a certificate, creating a trust-relationship with an inclusion list, or by installing it to a trusted location on the machine.

For more information about how to obtain a certificate for signing, see ClickOnce Deployment and Authenticode. You can add an inclusion list entry with a custom action in your Windows Installer file. For more information about enabling the inclusion list, see How to: Configure Inclusion List Security. If neither option is used, a trust prompt is displayed to the user to let them decide whether to trust the solution.

For more information about security related to document-level solutions, see Granting Trust to Documents.

The Setup and Deployment project templates are included with the Microsoft Visual Studio Installer Projects extension that is available for download. Visual Studio opens the File System Explorer for the new setup project.

The File System Explorer allows you to add files to the setup project. The setup project needs to deploy the ExcelAddIn. You can configure the setup project for this task by adding the ExcelAddIn project output to the setup project. The setup project needs to deploy the deployment manifest and application manifest. Add these two files to the setup project as stand-alone files from the output folder of the ExcelAddIn project.

Select the ExcelAddIn. Figure 3: Application and deployment manifests for the Add-in in Solution Explorer. These components must be excluded and deployed using prerequisite packages to allow them to be registered correctly. Also, the Software License Terms must be displayed and accepted before the installation begins.

The Utilities assemblies are meant to be deployed along with your application. In the Properties window, change the Exclude property to True to exclude the dependent assemblies from the setup project. Make sure to not exclude any Utilities assemblies.

You can configure your Windows Installer package to install prerequisite components by adding a Setup program, also known as a bootstrapper. This setup program can install the prerequisite components, a process called bootstrapping. For the ExcelAddIn , these prerequisites must be installed before the Add-in can run correctly:.

In the Prerequisites dialog box, select the correct version of the. I would like to be able to detect whether the VSTO runtime is present and advise the user before attempting to launch excel and failing if the VSTO runtime is missing.

Load "Microsoft. And that seems to mostly work. However, as it turns out, if the runtime had been installed and then uninstalled, this and other assemblies are left behind in the GAC and so it looks to my app as if the VSTO runtime is still installed. The following solution cannot be loaded because Microsoft Office support for the. NET Framework 4. What is excel checking for? Well, the point isn't to use the installer's launch conditions, but rather to be able to detect VSTO4 from an plain old windows app that is about to start excel and requires the VSTO runtime to be present.

The article referenced was sort of helpful, in that it explains that VSTO 4 is included with Excel , but only the. It appears that just by installing Office , the Microsoft.