Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The Outlook add-ins I have created using Visual Studio 2005 don’t use the ClickOnce installer, just the regular Windows Installer.
(File -> New Project -> Extensibility -> Shared Add-In)
I need to create the add-ins using the ClickOnce installer because as far as I know that’s the only way there is to sign the add-ins so they can run in spite of Macro Security settings on the clients’ computers.
Can someone tell me how to create an Outlook add-in installer using ClickOnce?
Add an installer project to your solution. That will install the application to your program files directory which is trusted by default. It will require the end user to have admin privileged to install, but it does not require the installer files to be signed. It is not technically a click-once install, but it works very well for office add-ins.
Edit: You also need to add a reference to the addin to the registry. Check out Deploying a Visual Studio 2010 Tools for Office Solution Using
Windows Installer on MSDN. Figure 6 and the instructions preceding it describe how this is done.
The actual values to add to the registry key can be a bit confusing, so here are the ones that I used which work fine:
"Provides functionality to access data from ...""CompanyTools"3(indicates that the add-in should be loaded at startup of the host application)"file:///[ProgramFilesFolder][Manufacturer]/[ProductName]/T360.Office.CompanyTools.vsto|vstolocal"Also, I think that you need to add Microsoft.VisualStudio.Tools.Applications.Runtime.dll as a dependency. I don’t think that it is by default.