I am working on a VSTO addin
I would like how to do that when the addin is going to be installed it's going to install a word template in the template folder together.
It seems like you need to create a custom action for your add-in installer where you could do the required actions programmatically while the add-in is installed.
There are two main ways deploying Office add-ins:
Deploy an Office solution by using Windows Installer
Deploy an Office solution by using ClickOnce
The windows installer (MSI) provides all the necessary tools for that.
Related
We're rolling out the VSTS Azure solution enterprise wide and have some users that will need to use a Citrix environment. Does anyone know if the TFS Office Addin (Office 2016) for work item updates, etc will work in a Citrix environment?
I know it installs to
C:\Program Files\Common Files\microsoft shared\Team Foundation Server\15.0\x86\TFSOfficeAdd-in.dll
Well, you can try below things to use the TFS Office Add-in on your Citrix VMs (Windows only):
Install Microsoft Office (Office 2016 in your scenario), then install
Visual Studio or at least install the Team Explorer, the TFS
Office Add-in will automatically integrate to office.
If you don't want to install Visual Studio/Team Explorer, then you can use the TFS
Office Integration Installer (Download from here). This new
installer just includes the Office integration component (Excel,
Project, etc) and is therefore lighter weight. See this blog : TFS
Office Integration Installer
You can reference this blog for details : Work with VSTS (or TFS) Work Items from Excel without installing Team Explorer
If you cannot see the Team ribbon in excel, you can refer to below article for troubleshooting: TFS-Office integration issues
We have a Microsoft word add-in that is working fine on the majority of pc's.
On a particular windows 7 pc, it has the visual studio 2010 tools for office installed correctly.
But when a user creates a new template word document, they get teh following error:
The customization assembly could not be found or could not be loaded.
You can still edit and save the document. Contact your administrator
or the author of this document for further assistance.
We have tried unloading all dependencies but still does not make any difference.
This is an issue effecting a small amount of windows 7 pc's with office 2016 installed. It seems to be pc related rather than the application.
Usually, the reason behind such an error is that the permissions for loading the VSTO solution are missing. One thing that often gets "missed" when deploying VSTO solutions is that the document must be in a "trusted location". You might want to check that this is the case by looking in the Word "Trust Center" (in the Options). You also need to be sure you've installed the correct version of the VSTO run-time for the version of Windows and Office. Read more about that in the Troubleshooting Run Time Errors in Office Solutions article.
Also it may indicate that you didn't include all required dependencies to your add-in's installer (any platform-specific assemblies). Something is missing on the target machines, so I'd suggest looking for any difference between machines. You can add the .NET Framework, the Visual Studio Tools for Office runtime, and the Office primary interop assemblies to your Setup package as prerequisites that are deployed with your Office solution. For information about how to install the primary interop assemblies, see Configuring a Computer to Develop Office Solutions and How to: Install Office Primary Interop Assemblies.
The required steps for deploying Office solutions are described in the following articles:
Deploying an Office Solution by Using ClickOnce
Deploying an Office Solution by Using Windows Installer
You can use the event viewer in Windows to see error messages that are captured by the Visual Studio Tools for Office runtime when you install or uninstall Office solutions. You can use these messages from the event logger to resolve installation and deployment problems. For more information, see Event Logging for Office Solutions.
See Troubleshooting Office Solution Deployment for more information.
I created an xll add-in which contains some user defined functions for excel using excel dna, now i want to deploy this add-in on the customer's pc, for that i would like to create an installer using installshield. is this possible to be done with installshield?
Have you an idea or any suggestion how to create an installer for my xll addin please ?
Many thanks
I am using Installshield for deploying VSTO 2007 Outlook plugin to all users. By default Office 2007 supports plugin deployment to current user only. I come across the follwing link which describes it http://blogs.msdn.com/b/mshneer/archive/2008/04/24/deploying-your-vsto-add-in-to-all-users-part-iii.aspx
A hotfix http://support.microsoft.com/kb/976811 is available but it is not redstributable.
Is there any easiest way available specially for Installshield.
Thanks,
Vinit
Change the registry path from HKEY_CURRENT_USER to HKEY_LOCAL_MACHINE in your setup project
I have a requirement to create an installer for an Outlook 2003 add-in that was created with VSTO.
We currently are using Wix for our installers as they play nice with MSBuild and I need to use it to create the installer for the outlook add-in.
I have no experience with outlook add-ins and am unsure exactly what is involved and how to go about creating the installer.
Can anyone share any experience/tips/examples that would help me please?
Thanks in advance,
B
I found this Microsoft article on VSTO add-ins deployment to be an absolute life-saver; I don't know about Wix, though. http://msdn.microsoft.com/en-us/library/bb332052.aspx
I've not done this in WiX but I have done it in InstallShield. Below with my notes from that time:
http://blog.deploymentengineering.com/search?q=vsto
One problem you will have is that WiX doesn't have a bootstrapper so you will have to find a way to chain the .NET Framework and VSTO redist ( also possibly the Office 2003 PIAs; you didn't say which version of VSTO you are using ) with your installer unless you choose to take the route that merely gates the install if those aren't found.
I recall using a DTF custom action to publish a certificate but I can't recall if that was needed for Office 2003 or only for Office 2007.