Vsto deployment setup project

Learn more. Asked 11 years, 8 months ago. Active 11 years, 6 months ago. Viewed 16k times. I am having some issues creating a setup file for my Outlook add-in. If I uninstall and reinstall using the same setup, it does not install properly. If I rebuild the setup, it installs fine again in other words, it only installs the first time a setup is run. This time, I can uninstall and reinstall as much as I want with the same setup. I am unable to remove this second set of registry entries as they do not appear anywhere in my setup project.

The issue with leaving them there is that the add-in executes every command twice since it is registered twice. Improve this question. Is ClickOnce not an option? I've never done click once, but I don't think it is an option. We don't want to publish to a server at this time — i8abug. However, if you update the solution, you must distribute a new setup program. See Deploy an Office solution by using Windows Installer.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Please run Setup.

The launch condition above explicitly checks for the presence of the VSTO runtime when it's installed by the bootstrapper package. Select the Search for RegistryEntry1 search condition, right-click the condition, and select Properties Window. The version numbers maybe different for you depending on the versions of the runtime that your Add-in requires. If an Add-in targets. If the value is set to True , then the Types are being embedded and you can skip down to the To build the setup project section.

Right-click Search for Component1 and click Properties Window to show the properties of the launch condition. You can further refine the launch conditions for the ExcelAddIn installation. For instance, it maybe useful to check if the actual target Office application is installed. Deploying document-level solutions require a few different configuration steps in the Windows Installer setup project.

Properties inside an Office document are used to locate document level solutions. If the document is installed to the same folder as the VSTO assembly, no changes are required.

However, if it's installed to different folder, these properties will need to be updated during the setup. For more information about these document properties, see Custom Document Properties Overview. The following example uses a document-level solution called ExcelWorkbookProject and a setup project called ExcelWorkbookSetup.

The ExcelWorkbookSetup project is configured by using the same steps outlined above, except for setting the registry keys. Add a new. This value is retrieved from the Visual Studio project file. On the Build menu, click Build Solution to build the document-level solution and add the solution ID property to the project file. Click Yes in the dialog box that appears to close the ExcelWorkbookProject editor.

The last step is to configure the custom action for the Install and Uninstall steps. Select Primary Output and click OK to close the dialog box and add the assembly containing the custom action to the setup project.

Name the custom action Copy document to My Documents and attach customization. Name the custom action Remove document from the Documents folder. The SolutionID is also needed. The Custom Action for Uninstall needs the name of the document, you can provide that by using the same documentLocation parameter in the CustomActionData.

Office Primary Interop Assemblies. Custom Document Properties Overview. Specifying Form Regions in the Windows Registry. Granting Trust to Documents. NET technologies. Wouter is a frequent contributor to developer community sites such as MSDN. He has published several white papers and articles as well a book available on line titled Open XML: Explained e-book. Wouter is the founder of Code-Counsel, a Dutch company focusing on delivering cutting-edge technical content through a variety of channels.

You can find out more about Wouter by reading his blog. Since that time, Ted has been entirely focused on educating professional developers on SharePoint technologies. Skip to main content. This browser is no longer supported.