VSTO Runtime Update to Address Premature WPF UI Thread Shutdown

In the VSTO Runtime released a month and a half ago (version 10.0.50701), a small regression was inadvertently introduced, which is fixed in today’s update to the runtime. The issue impacts add-ins that call Globals.Factory.GetVSTOObject on a Word document or Excel workbook.  If Windows Presentation Foundation (WPF) is used for the add-in’s user interface, and… Read more

Visual Studio 2013 Update 3 released

Earlier today, Visual Studio 2013 Update 3 was released.  This update offers a number of small but useful enhancements for VSTO developers:   #1:  Support for .NET 4.5.2 and beyond, and the de-coupling of Office versions from .NET versions. We heard a lot of feedback on this on MSDN forums, with developers asking to mix-and-match… Read more

VSTO Runtime Update to Address Slow Shutdown on .NET Framework 4.5.2

In a VSTO Runtime release earlier this year, we addressed an issue of slow application shutdown for add-ins using WPF controls on touch-enabled devices. With the release of .NET Framework 4.5.2 two months ago, and the increased usage of our latest runtime “in the wild”, we received customer feedback that the latest .NET 4.5.2 version… Read more

Guest Post: Resources Available for VSTO Developers Wishing to Customize the User Interface

[Guest Post by Marty Andren, Premier Field Engineer at Microsoft] As a Microsoft Premier Field Engineer / Office Developer, a question I’m often asked when helping customers develop VSTO solutions is how to customize the user interface when building out their application. This question is not as simple as it sounds, as the approach used… Read more

VSTO Runtime Update to Address Slow Shutdown and “Unknown Publisher” for SHA256 Certificates

We are pleased to announce a new version of the VSTO Runtime (10.0.50325) that addresses two important issues reported to us by customers. For VSTO add-ins using WPF controls, customers using touch-enabled devices experienced a 15-20 second lag when closing Office applications. This issue was first reported via a Connect bug, which helped provide the… 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

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

Fixing Compile and Run Time Errors after Retargeting VSTO Projects to the .NET Framework 4 (McLean Schofield)

Now that Visual Studio 2010 is released, some of you might be itching to upgrade your existing VSTO projects so that you can take advantage of the new features in the .NET Framework 4 that improve the Office development experience. Or, you might have already started using Visual Studio 2010 to develop a VSTO project… Read more

Why Should I Upgrade from .Net Framework 3.5 to .Net Framework 4 ? (Navneet Gupta)

I was chatting with some of my friends about Visual Studio 2010 and .Net Framework 4 and they asked me why should they move their application to .Net Framework 4, I am answering the question here for everybody to benefit. Frankly speaking there is no definitive answer; it is like there is no single pill… Read more

Why is FrameworkVersionMismatchException thrown? (Hamed Ahmadi)

The “Microsoft.VisualStudio.Tools.Applications.Deployment.FrameworkVersionMismatchException” is thrown due to the specific implementation of how VSTO 2010 runtime loads the appropriate CLR to install a VSTO customization. This exception is thrown when both .NET Framework 3.5 (CLR 2.0) and .NET Framework 4 (CLR 4) are installed on a machine and a VSTO customization which targets .NET Framework 4 is… Read more