Discuss and ask questions about using Visual Studio to create managed code solutions for Microsoft Office.
Office Developer Tools for Visual Studio 2012: Now Available with Office 2013 and .NET Framework 4.5 support
I'm pleased to announce that the official Office Developer Tools for Visual Studio 2012 is now available to download! For VSTO developers, this release brings .NET 4.5 support and design-time support for Office 2013, along with general design-time enhancements and bug fixes to the VSTO Runtime (released separately a few months ago via our download center and Windows Update; see KB 2796590 for information regarding the Runtime). We also heard your feedback from "Preview 2" of the tools, including the request to bring back the VSTO Runtime Bootstrapper into VS 2012 -- it is now back in the product.
Office Developer Tools for Visual Studio 2012 also includes tooling for the new apps for Office and apps for SharePoint projects, improvements to SharePoint Workflows, and more. You can read the official announcement for apps-related tooling on Soma’s blog post.
VSTO Office 2013 design-time support in Visual Studio 2012.
Note: Now that's we've added .NET 4.5 support to 2013, we've properly re-categorized the templates in the "New Project" dialog according to the .NET framework version that they support. So, if you're looking for the Office 2010 templates after installing the latest tools, be sure to adjust the ".NET Framework" dropdown to ".NET Framework 4.0". Again, to recap, both the 2010 and 2013 templates support .NET Framework 4.0, but only the 2013 templates support .NET Framework 4.5 -- and the "New Project" dialog respects that categorization.
I hope you enjoy using our new tools! If you have any questions or comments, please don't hesitate to reach out to us.
- Michael Zlatkovsky | Program Manager, Visual Studio Tools for Office & Apps for Office
"New Item" templates not available for VSTO project migrated from VS 2010 to VS 2012
For those migrating a VSTO project from Visual Studio 2010 to VS 2012, there appears to be an issue where Office items (such as the Ribbon) are not available in the converted project. Fortunately, there is an easy fix. See Maarten van Stam's (MVP) blog post http://maartenvanstam.wordpress.com/2012/12/22/office-templates-not-available-in-vs2012-with-converted-project/ for a quick way to resolve the issue.
Documentation for Office 2013 Ribbon controls now availableCindy Meister MVPMVPThursday, January 10, 2013 7:49 AM
I know the documentation for Office 2013 is still somewhat limited, but hopefully the following link will help.
Microsoft Office Document: [MS-CustomUI2] Supporting Documentation - http://www.microsoft.com/en-us/download/details.aspx?id=727
From here, you should be able to download the *.txt files for Word, Excel and PowerPoint, plus the imageMso information. Once a file is downloaded, it can be opened in Excel to make it easier to look through all the controls.
Microsoft Online Community Support
VS2012 & Office2010 solutions: Add-ins disable / Customization could not be loadedCindy Meister MVPMVPThursday, December 13, 2012 6:39 AM
We had discovered an issue where add-ins deployed using the ClickOnce method will, under certain conditions, try and fail to install an update, and thereby disable the add-in. For document-level customizations, an exception window with a stack trace may be shown; for application-level add-ins, the add-in will be disabled silently. See the thread http://social.msdn.microsoft.com/Forums/en-US/vsto/thread/495098f8-6364-443a-b2e1-23e650af7e1e.
There is now a NEW VERSION of the VSTO Runtime that fixes the issue. If you're using the web bootstrapper (for add-ins developed using Visual Studio 2010), the bootstrapper will automatically chain in the latest version, so no action is required on your part, or on that of your users. If you're deploying from Visual Studio 2012, you'll need to enable the bootstrapper functionality manually: please see http://blogs.msdn.com/b/vsto/archive/2012/12/21/creating-a-bootstrapper-package-for-an-office-2013-vsto-add-in-with-visual-studio-2012.aspx. Users can also download the latest runtime from http://go.microsoft.com/fwlink/?LinkId=140384.
Installing the new Runtime is a preventative measure, and we highly recommend that all of your users do so! However, this will not fix add-ins that may already have gotten disabled due to the issue. Thus, for users who are already impacted:
If the install location is still accessible (and/or if the developer puts a new version into the same location)
1. Re-run setup from the original network share.
2. Re-enable the Add-In / Doc-Level Customization from within the Office application, as described below.
If the install location is NOT accessible (e.g., network share permanently down, or file was installed off of a USB stick which has since been removed)
1. Launch “regedit.exe” from the start menu / start screen. Navigate to Computer ==> HKEY_CURRENT_USER ==> Software ==> Microsoft ==> VSTA ==> Solutions.
2. There should be several entries there, identified by GUIDs. Click on each entry and check the “ProductName” data until you find the Add-In that you’re trying to re-enable.
3. For the Add-In that’s having problems, double-click on UpdateEnabled.
4. Change the “Value data” to 0 and press “OK”. This will disable Update Checking (and hence cure the problem) until a new version of an add-in is explicitly installed, or until the user repeats the same steps, and sets “UpdateEnabled” to “1”.
After editing the Registry, the user should re-launch the Office App (e.g., Excel), and go through the usual steps of re-enabling the add-in (see below).
The usual steps of re-enabling the add-in: (required in either case for any user with currently-disabled add-ins)
1. Open the application’s options (e.g., “Excel Options”) and navigate to the Add-Ins tab.
2. Select “COM Add-ins” from the “Manage” dropdown.
3. Press “Go…”. A window will open.
4. Enable the checkbox for the Add-In(s) that you’d like to re-enable.
5. Click “OK”.
After performing the above steps, the add-in / document-level customization should re-activate in the host application, and also show up in the Control Panel’s “Add or Remove Programs” list.
Michael Zlatkovsky | Program Manager, Visual Studio Tools for Office & Apps for Office
Filtering and SortingUse these options to narrow down the question and discussion list.
- 1215671Michael Zlatkovsky Thursday, December 02, 2010 3:24 PM
- 123781Harry Miller - MSFT Wednesday, June 18, 2008 5:20 PM
- 136830Cindy Meister MVPMVPSunday, May 25, 2008 11:25 AM
- 151047Mary Lee - MSFTMicrosoft EmployeeTuesday, October 21, 2008 4:34 PM
- 144926Ji.Zhou Sunday, February 08, 2009 1:59 PM
- 065867Cindy Meister MVPMVPSunday, May 25, 2008 10:12 AM
- 78736873NewtoCsharp2008 Tuesday, October 11, 2005 10:49 PM
- 453108Ed.A Thursday, October 13, 2011 12:51 PM
- 431956Ram Amos Sunday, May 06, 2012 10:52 AM
- 4216992Pavan Kulkarni Tuesday, April 18, 2006 10:38 AM
- 396106Jahedur.Rahman Thursday, August 05, 2010 10:39 AM
- 3814868Abhishek Chadha Tuesday, October 10, 2006 7:24 AM
- 3698560mrleokarthik Wednesday, January 10, 2007 11:51 AM
- 359529Jonathan Miller Friday, May 25, 2007 9:49 PM
- 354203vermaanubhav Tuesday, September 27, 2011 3:23 PM
- 34141729IainDowns Wednesday, January 10, 2007 4:14 PM
- 3413995CJM3407 Thursday, June 10, 2010 4:00 PM
- 333904Howard Mansell Tuesday, September 04, 2012 8:08 PM
AddIn originnaly writen for Outlook 2010 can not load file or assembly 'Microsoft.Office.Interop.Outlook, Version=220.127.116.11Filip Mateasko Thursday, April 11, 2013 12:01 PM
- 3210825Hong (MA, USA) Wednesday, August 31, 2011 6:19 PM
- 3235772Hussain Saffar Wednesday, August 02, 2006 3:59 PM
microsoft.office.core.commandbarcontrol commandbar.findcontrol returns object reference not set to an instance of an objectShailendra_G Friday, January 07, 2011 5:08 PM
- 302719ArchanaSinghvi Saturday, December 10, 2011 6:51 AM
- 302353noobie1 Wednesday, January 18, 2012 4:29 AM
- 2914040MauricioUY Friday, December 08, 2006 11:58 AM
- 2924220mafiaboy Thursday, October 11, 2007 9:36 AM