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.
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 want to create a Add-In. I will create in VS 2013. I just don't know what is minimum version support of Ms Office.
Can anybody please suggest me? So, I can take case of the requirement.
VS2013 will natively support 2010 and 2013, but it is possible to support 2007 as well.
Per Microsoft's article on running solutions in different version's of Office:
If you developed solutions for Office 2010, you can run the same solutions in Microsoft Office 2013. If your customer base uses the 2007 Microsoft Office system, you can use Visual Studio 2013 to develop solutions that work in all three versions of Office. In this scenario, the solution will run without errors in the 2007 Microsoft Office system only if the solution doesn’t use features that are new in later versions of Office. Microsoft Office applications can also run solutions that were created by using a previous version of Visual Studio.
I am trying to create a new SharePoint project in my virtual machine. it has SharePoint 2013 installed.
I am using visual studio 2010 ultimate version.
Every time i try to create a new empty SharePoint, web part or any SharePoint project it says.
A SharePoint server is not installed on this computer. A share Point server must me installed to work with SharePoint projects
but i have SharePoint 2013 installed.
can we use VS 2010 to create SharePoint projects in a VM with SP2013 installed.
I just installed the office developer tools for VS 2010 as well. But still i get the same results.
Any ideas.
This link describes the problem and how to fix it
So, have you installed Office Developer Tools for Visual Studio 2012? The default SharePoint project templates come with VS2012 is for SharePoint 2010 and will not work in SharePoint 2013 Server.
Also you need to make sure the site against which you are developing farm solution doesn't use developer template (rather user team site template).
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.
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