Develop Office Client Applications using Visual Studio
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 context for investigating and fixing this bug.
Additionally, for developers using SHA256 code-signing certificates, the installation Trust Prompt would erroneously display “Unknown Publisher” even when the publisher was fully trusted. The latest update ensures that the publisher’s name and verification status are properly displayed.
As always, the latest version of the VSTO Runtime is available for download at http://go.microsoft.com/fwlink/?LinkId=140384. The update will also be distributed as part of Windows Update in the future. If you would like to ensure that your users have the latest version installed, please follow the instructions for creating/modifying a bootstrapper package from our previous blog post, substituting the latest version number (10.0.50325) into the following properties:
<BypassIf Property="VSTORuntimeVersionInstalled" Compare="VersionGreaterThanOrEqualTo" Value="10.0.50325"/> <BypassIf Property="VSTORuntimeVersionOfficeInstalled" Compare="VersionGreaterThanOrEqualTo" Value="10.0.50325"/>
<BypassIf Property="VSTORuntimeVersionInstalled" Compare="VersionGreaterThanOrEqualTo" Value="10.0.50325"/>
<BypassIf Property="VSTORuntimeVersionOfficeInstalled" Compare="VersionGreaterThanOrEqualTo" Value="10.0.50325"/>
We would like to thank our customers who brought these issues to our attention.
~ Thomas Bombach | Software Development Engineer, Visual Studio
Is Microsoft going to do active development on VSTO or should developer start moving to Office.js. Is VSTO just like linq-to-sql and Office.js is to Entity Framework? Be honest Microsoft!
Thanks for your question Ben, we have already publically announced that we will not be turning off VSTO or VBA in the next version of Office. All of our new investments are in Apps for Office and Apps for SharePoint and making the Office 365 APIs more robust. We will not be making any future investments in VSTO or VBA.
The good news is that we are looking for feedback on this on UserVoice (officespdev.uservoice.com) so that we can prioritize based on real world feedback, so we encourage you to submit your ideas.
I highly recommend you keep following the progress of this on the VSTO blog http://blogs.msdn.com/b/vsto/ and Office blog http://blogs.office.com/ . Very shortly we will be publishing an update to the blog post (blogs.msdn.com/.../roadmap-for-apps-for-office-vsto-and-vba.aspx) with a 3 to 6 month roadmap of what we’re thinking internally right now.
We appreciate your support and look forward to the great solutions you will all build on Office 365!
Technical Product Manager - Office 365
Our testing of this update shows that when you have SQL Server 2012 PowerPivot for Excel (32-bit) 11.1.3129.0 (SP1) install with Excel 2010 (all public updates), Excel now takes about 10 seconds to shut down.
Upgrading to SQL Server 2012 PowerPivot for Excel 11.2.5058 (SP2) does not fix the issue.
The only thing we have been able to is revert back to Visual Studio 2010 Tools for Office Runtime 10.0.40303. Excel then shuts down as quick as expected.
It only seems to be an issue when both the latest VSTO *and* any PowerPivot is installed.
This should be easily reproduceable.
We have received a couple of reports last week about the re-emergence of this issue, and are hard at work on a fix. The culprit is a behavioral change in .NET 4.5.2, recently released. We are in the final stages of validating our fix, and hope to have it on the Download Center shortly. We will post to the VSTO blog when the new runtime is ready. There is also a “Connect” bug tracking this, connect.microsoft.com/.../stylus-input-thread-lags-when-closing-application-with-vsto-add-in-using-wpf.
Is there something else that you did that installed .NET 4.5.2 on your computer, or are you saying that it was PowerPivot that somehow installed it?
Thanks for reporting the issue, and apologies for the inconvenience this has caused,
- Michael Zlatkovsky | Program Manager, Visual Studio
Just letting you know that this update when combined with .NET Framework 4.5.2 actually causes a 15-second delay when closing Office programs that have VSTOs loaded (such as PowerPivot).
I'm working with Premier Support because we can't deploy this update until the issue is resolved.
If you want to check the case notes, it's case REG:114070811599747.
Sorry for the doubled-up information in my last post.
We like to be fully-patched. We chose to deploy .NET 4.5.2, as it cuts down image deployment time. We love the idea of cumulative .NET updates and this is the closest thing we have to that.