Visual Studio 2013 VSTO not creating Word 2010 project - visual-studio-2013

I'm trying to develop a Word Document add-in through Visual Studio 2013, using a Word 2010 Document selected from the Visual Studio project menu of Office/SharePoint Office Add-ins. It is needed to tie in SharePoint 2013 with a collaborative Word document. I keep getting the error message:
Project cannot be created because the "Word Visual Studio Design-Time Adaptor Add-in" is not working correctly. Word might have disabled the add-in or made it inactive, or all add-ins might be disabled in your Trust Center settings. Check the add-in status in Word Options. If the add-in is active and enabled, reinstall or repair Visual Studio Tools for Office.
I have checked that there is no disabled add-ins in the Trust Center, and I do see the Visual Studio Tools for Office Runtime in the Add-ins. I cannot find any other options, as I have reinstalled the Visual Studio Tools for Office as well.
Where should I go from here?

I had the same problem, turned out that one of the updates was causing the problem. (Breaking the VSTO plug-in in some way)
What I did was reinstall Office, and I manually told Microsoft Update not to install updates that were launched after Oct 2016, I could then create Document-Level projects again.

Related

Missing Outlook 2013 Add-in

I am working on making a Outlook Add-in for Outlook 2013. The issue is, I use Visual Studio 2010. I did some googling and found that I need the Developer Tool Kit and it lead me here. I installed the tool kit, but I am still not seeing any new Templates. What am I doing wrong, or what can I do to get that Outlook Add-in?
Thanks in advance!
Unfortunately VSTO allows creating version-specific add-ins. VSTO 2010 (Visual Studio 2010 Tools for Office Runtime) is shipped with Visual Studio 2010 Professional edition or above. It supports creation and editing of document- and application-level add-ins for Office 2007 and Office 2010. You need to use later Visual Studio versions for creating COM add-ins for Office 2013. However, you can run solutions in Office 2013 that were created in earlier Visual Studio versions, see Running Solutions in Different Versions of Microsoft Office for more information.

Visual Studio 2013 refuses to work with Office 2016

I'm trying to create projects in Visual Studio Pro 2013 for use in Office 2016. I know it's supposed to be possible, but VSTO seems to insist I need Office 2013.
I've followed several MSDN walkthroughs (Add-In, Document-level, custom tab), and always end up with errors like these:
I checked the registry, and my .NET framework is version 4.6.1. I added the runtime and targeting packs for 4.6 and 4.6.1 to Visual Studio, but keep getting the same results.
The errors come up when I get to the "hit F5 to run the project" step. Any suggestions or solutions?
Background: I'm an MS Word forms developer in a corporate environment. Of our 1,000-or-so forms, about 100 of them have custom toolbars, which haven't been available since the ribbon interface after Office 2003. We modify them with a non-networked machine using the old software. I've been tasked with finding a way to regain functionality similar to custom toolbars in Office 2016, our current baseline. The only version of Visual Studio available to me is VSTO Pro 2013.
Your Excel Project => Properties => Debug tab => Start external program
Set it into excel 2016
The path like C:\Program Files (x86)\Microsoft Office\Office16\EXCEL.EXE
If you cannot debug after that, try to attach the process to debug using Visual Studio.

Outlook code review link opens wrong Visual Studio version

I have Visual Studio 2013 Premium and 2012 Premium installed. I get email notifications for code reviews in TFS. These notifications include a link to open the reviews, with display text "Open Changes and Comments in Visual Studio". The link location starts with
vstfs://codereview/...
When I click the links, the code reviews are opened in Visual Studio 2012.
How can I make Visual Studio 2013 handle the code review email links instead of Visual Studio 2012? I would like for them to be opened in Visual Studio 2013, instead.
Open "default apps" on Window,
Select "Choose default apps by protocol" and scroll until you see "VSTFS"
Select "Microsoft Visual Studio Web Protocol Handler Selector" and test the options.
Open your registry and modify the path to devenv.exe defined in the key HKCR\vstfs\Shell\Open\Command\(Default)
I repaired my Visual Studio 2013 installation and changed all of the filetypes associated with Visual Studio 2012 to be associated with 2013 in the Default Programs tool, and then restarted my PC. The problem is now resolved, but I don't know what fixed it; my guess is the 2013 repair.

Can I create an Outlook 2010 add in in Visual Studio Professional 2013?

I have just installed Visual Studio Professional 2013 and wish to write an add in for Outlook 2010, however there is only an option to start a new project for an Outlook 2013 add in. When I search for more templates under the web option I can not find what I want. Is there a way to create an Outlook 2010 add in without installing a different version of Visual Studio? Or will a 2013 add in work in 2010?
At the New Project dialog, first change the .NET Framework target version to 4.0. Combobox at the top of the dialog. You'll then see the Office 2010 project templates as well.

Installing Visual Studio Tools for Office System

I have VS 2008 Standard and I'm trying to open a project that is a plug-in for Outlook, the project fails to load showing the message
"C:\Program Files\MSBuild\Microsoft\VisualStudio\v9.0\Office
Tools\Microsoft.VisualStudio.Tools.Office.Office2007.targets was not
found".
The Office Tools directory is missing yet I have installed the Office 2007 Primary Interop Assemblies and the Visual Studio Tools for the Microsoft Office system 3.0.
What am I missing?
Visual Studio Tools for Office (VSTO) is not included with Visual Studio Standard (Source: http://msdn.microsoft.com/en-us/library/bb398242.aspx). When you installed VSTO 3.0, you only installed the run-time components, which only lets you run published VSTO solutions, not design them in Visual Studio.
You will need to upgrade to either Visual Studio Team System or Visual Studio Professional.

Resources