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 MVPMVPquinta-feira, 10 de janeiro de 2013 07:49
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 MVPMVPquinta-feira, 13 de dezembro de 2012 06:39
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
Filtragem e ClassificaçãoUse essas opções para refinar a lista de discussão.
- 1215668Michael Zlatkovsky quinta-feira, 2 de dezembro de 2010 15:24
- 123776Harry Miller - MSFT quarta-feira, 18 de junho de 2008 17:20
- 144917Ji.Zhou domingo, 8 de fevereiro de 2009 13:59
- 151030Mary Lee - MSFTMicrosoft Employeeterça-feira, 21 de outubro de 2008 16:34
- 136828Cindy Meister MVPMVPdomingo, 25 de maio de 2008 11:25
- 065855Cindy Meister MVPMVPdomingo, 25 de maio de 2008 10:12
- 03SDAgem há 7 minutos
- 08zinzolin há 23 minutos
- 4132ewolters terça-feira, 21 de maio de 2013 13:17
- 019Developer_29 há 2 horas 16 minutos
- 76030Ajit Singh segunda-feira, 6 de setembro de 2010 08:25
- 3128Sendi_34 terça-feira, 21 de maio de 2013 04:31
- 4104FanhaoKong sexta-feira, 17 de maio de 2013 02:47
- 95384FerchoArg terça-feira, 21 de setembro de 2010 15:31
- 159Divyans Mahansaria segunda-feira, 20 de maio de 2013 06:59
- 170Divyans Mahansaria segunda-feira, 20 de maio de 2013 06:58
- 298Thomiouf sexta-feira, 17 de maio de 2013 09:01
- 297Lucas Cordina segunda-feira, 20 de maio de 2013 15:47
- 9275Arthur Gardner quinta-feira, 9 de maio de 2013 15:17
- 182菜鸟与孤鹜齐飞 segunda-feira, 20 de maio de 2013 01:22
Visual Studio 2010 Pro, Office 2007 installed on WS2008RC ... File/New Project/Visual Basic/Office2007/Outlook2007Add-in ... fail @ Signing/Create Test Certificatelypoten quarta-feira, 13 de outubro de 2010 23:35
- 3116Gaurav Kukreja terça-feira, 14 de maio de 2013 07:46
- 159Super SAD terça-feira, 21 de maio de 2013 05:22
- 5103Digital604 domingo, 19 de maio de 2013 16:21
- 261WordRake segunda-feira, 20 de maio de 2013 20:49
- 2106WordRake quinta-feira, 16 de maio de 2013 02:16