I have developed an excel addin using VSTO in C#.net .Now i want to deploy this addin in other machines too .So that users who installed this can see my addin in excel menu -> Addins-> MyAddin
Alternatively can i give them just Excel with myaddin.So that whoever has this Excel can access addin and use it.This way they don't see myaddin in every excel file addins menu.
You can use a Visual Studio 2010 setup project to create a Windows Installer package. See this MSDN Link
Quote from that Link
Summary: Learn how to deploy a Microsoft Visual Studio Tools for the
Office system 2010 add-in or document- level solution using a Visual
Studio 2010 setup project to create a Windows Installer package that
targets the 2007 Microsoft Office system or Microsoft Office 2010.
Wouter van Vugt, Code Counsel
Ted Pattison, Ted Pattison Group
This article was updated by Microsoft with permission from the
original authors.
Applies to: Visual Studio 2010 Tools for Office, 2007 Microsoft Office
system, Microsoft Office 2010, Visual Studio 2010.
Download: http://code.msdn.microsoft.com/VSTO2010MSI
Contents
Overview
Deployment Methods
Deploying Office solutions that target the Visual Studio 2010 Tools for Office runtime
Download Samples Provided with this Article
Creating a Basic Installer
Conclusion
Additional Resources
About the Authors
EDIT
You may also see this link for All Users.
Conceptually, all you need to concentrate on is get yourself a COM object created which must be running even when the application (MS Excel here) is not open in the explorer.
More can be figured out from the following link :
http://www.codeproject.com/Articles/7859/Building-COM-Objects-in-C
(P.S : link is for c# not c).
Next you should give your users a .exe file including code to create the COM object.
Related
After creating Office Add-In template project, on execution I am getting an error which says application isn't installed in this computer.
What should I have to install? I ave already installed Office Tools from Visual Studio installation.
I have Visual Studio 2017 Project Type was : Office Add-In ( PowerPoint Web Add In) Office version is : 2007
A Web Add-in (which uses the Office JS APIs) only works with Office 365. You'd need to create a VSTO project for an Add-in that runs in any earlier version of Office.
I'm trying to apply instructions of an MSDN article Create add-ins for Access web apps to create my own add-in for MS Access web application. I have Visual Studio 2015 Update 1 and MS Office Professional Plus 2013 installed but I can't find an Office Add-In template. I have tried to search for this Office Add-In template online (from within VS 2015) but I have failed to find it. How I can make this Office Add-In template installed for VS 2015 Update 1?
Please see attached picture for the step where I have got stuck.
The Latest Microsoft Office Developer Tools for Visual Studio 2015 setup including project templates for MS Access Web Apps Office Add-Ins can be downloaded/run via Web Installer from this link http://aka.ms/GetLatestOfficeDevTools.
While using Visual Studio 2013/C# to create Excel automation ... I have both Office 2010 and Office 2013 on my machine. How do I create an add-in that will install into Excel 2010 or on another case install into 2013, my choice. Will creating a new 2010 or 2013 add-in project do the trick or do I have to configure something to steer it to one or the other? Thanks
You have to create an add-in per version of Office you wish to target. i.e. one for 2010; another for 2013 and so forth. The Office types used in each add-in are locked to that version of office. COM and Automation does allow you to create objects from version-independent PROG IDs but that's another story.
However if done right, you could abstract out some of your core code to be shared across Office installations.
I am currently in the process of re-writing some VBA macros that were written for office 2003. I was wondering if I wrote a C# add-in for 2007, if it would work for 2010 or maybe even 2013. Or if I wrote them for 2010 if they would work for 2007 and 2013 as well. I currently have access to 2007 but I could get access to 2010 if need be, no 2013 yet.
So, basically, how much does the version of office affect the plugins?
If you use Visual Studio Tools for Office 2010 (VSTO 4.0) then it will compatible for Office 2007 ,Office 2010 and with Office 2013.If you use earlier version other than the above then you can use that only for particular office versions only.As a example VSTO 3.0 only supports office 2003 and 2007 as shown below table.
For more information check this out Visual Studio Tools for Office and Visual Studio 2010 Tools for Office Runtime
compatibility Shows like below:
I hope this will help to you.
you can take a look at Netoffice, a wrapper for MS Office that enables you to create Addins for all supported versions of MS Office. You don't need VSTO and you can check within your own code which version of Office your AddIn is running in.
We need to create a VSTO add-in in C# that supports both Outlook 2007 and 2010.
To start off we created 3 projects:
File->New Project->Office->2007->Outlook 2007 Add-in
File->New Project->Office->2010->Outlook 2010 Add-in
File->New Project->Windows->Class library
All shared code is in project #3.
So far, we have partially developed the add-in and have been using ClickOnce deployments for testing.
One day, we noticed someone installed the 2010 add-in for 2007 Outlook and had no ill effects whatsoever.
So a few questions:
Is there any reason to create the
2007 VSTO project? Can we just
create the 2010 project?
Or is the only difference the version of
the office runtime that is
bootstrapped by the ClickOnce
installer? Can you just install the 2010 runtime for Outlook 2007?
If there is no difference, why are
there two Visual Studio project
templates?
In our final solution, we will be using a WiX installer, which is also working thus far. The WiX installer will be simplified greatly if we can use 1 project for the add-in.
Is there any reason to create the 2007 VSTO project? Can we just create the 2010 project?
You can just use the 2010 project, but if you accidentally reference any 2010 ONLY api's, for example accessing any of the new conversation API's will cause your add-in to blow up in 2007.
Or is the only difference the version of the office runtime that is bootstrapped by the ClickOnce installer? Can you just install the 2010 runtime for Outlook 2007?
Basically you are writing a VSTO 3.0 add-in, which works for both 2007 and 2010. VSTO doesn't actually care which template you are writing for, only that your add-in is a VSTO 3.0 add-in.
If there is no difference, why are there two Visual Studio project templates?
2 reasons that I can see, F5 debugging support, and to make sure you do not access a new API'
If you do go down the only 2010 add-in road, I suggest you do a compile of the solution against the Microsoft.Office.Interop.Outlook v12 PIA which will show you any new API's that you are accessing. If you do want to target some of these new API's only IF your add-in is hosted in 2010 then have a look at http://blogs.msdn.com/b/vsto/archive/2010/06/04/creating-an-add-in-for-office-2007-and-office-2010-that-quot-lights-up-quot-on-office-2010-mclean-schofield.aspx