Performance Improvements Coming Soon to a Service Pack Near You (Stephen Peters)

With the SP1 work winding down, I thought that I’d take a moment and discuss three new performance improvements that are going into VSTO for SP1. We have listened to your feedback and understand that startup time is a major issue, and so we have focused on attempts to make the VSTO runtime load faster…. Read more

Microsoft Help Viewer 1.1 – Updates Planned for Visual Studio 2010 SP1 (Kathleen McGrath)

Paul O’Rear, a Program Manager on the Library Experience team, describes the changes to the Microsoft Help Viewer planned for Visual Studio 2010 SP1. He demonstrates the new functionality of the viewer in an early build of Help Viewer 1.1. See Microsoft Help Viewer – Updates Planned for Visual Studio 2010 SP1 You can learn… Read more

Installing Office 2007/VSTO 3.0 Solutions on Computers with Office 2010 (Mary Lee)

You have probably been reading and hearing about Microsoft Office 2010 for some months. Now, you may be wondering how much work is necessary to install your existing Office 2007/VSTO 3.0 solutions on customer computers that have Office 2010. Perhaps you’re thinking about migrating the Windows Installer Setup projects or ClickOnce deploymen projects? The answer… Read more

Office 2010 PIA BootStrapper Released (Beth Massi, Lily Ma)

Today we released the Microsoft Office 2010 Primary Interop Assemblies (PIA) Bootstrapper Installer which adds the Microsoft Office 2010 Primary Interop Assemblies to the Prerequisites Dialog Box in Visual Studio 2010 or Visual Studio 2008. Then when you deploy with ClickOnce or Windows Installer, you can select this option to deploy the Microsoft Office 2010… Read more

Deploying Microsoft Office Solutions by Using Visual Studio 2010 and Windows Installer (Mary Lee, Saurabh Bhatia)

In Visual Studio 2010, you can use the ClickOnce and Windows Installer deployment technologies to deploy Office solutions that target both Microsoft Office 2007 and Microsoft Office 2010. The main advantage of using Windows Installer to deploy your Office solutions is to install application-level add-ins to AllUsers, rather than the current user only. There are… Read more

Channel 9 Interview: Office Add-in (VSTO) Performance Tips & Tricks (Beth Massi, Stephen Peters)

In this interview, I sit down with Stephen Peters, a developer on the Office client tools team in Visual Studio. Steve shows us a couple of tricks for how you can squeeze the best performance out of Office solutions built with Visual Studio (VSTO). He also shows how to finely control the way your custom… Read more

Sharing a Ribbon Customization Between Office Projects in Visual Studio 2010 (McLean Schofield)

A customer on the VSTO forums recently noticed that the steps we blogged about for sharing a single Ribbon customization between multiple projects in Visual Studio 2008 no longer works in Visual Studio 2010. When following the instructions in the blog post, you get an error when you try to open the Ribbon code file… Read more

Open XML Package Editor Power Tool for Visual Studio 2010 (Navneet Gupta)

Update (June 5th, 2014):  We have released an update to the Open XML Package Editor Power Tools, to make it compatible with Visual Studio 2012 and 2013, and to support Visio’s VSDX format.  In addition, the project is now open-sourced.  We hope you enjoy using it – and if you have questions, leave feedback on… Read more

Troubleshoot VSTO Add-In Load Failures (Navneet Gupta)

We have helped many developers in troubleshooting VSTO add-in load failures. Hamed has written a very nice blog post explaining the basic steps to troubleshoot VSTO add-in load failures. Even if you have not faced this issue yet, I recommend reading the post because it contains basic information about Office add-ins that developers should know…. Read more

Creating an Add-in for Office 2007 and Office 2010 that "Lights Up" on Office 2010 (McLean Schofield)

Managed Office add-ins traditionally have been able to run in the targeted application (the version of the application whose PIAs the add-in references) and in later versions of the application. Therefore, if you need to create a single VSTO add-in that can be run in multiple versions of an application, the typical guidance is to develop the add-in by using a project template… Read more