An update rollup is available that resolves several issues in Microsoft Visual Studio 2010 Tools for Office Runtime 4.0. The release date for this update is January 8, 2013.
This update rollup affects add-ins for the 2007 Microsoft Office system, Microsoft Office 2010, and Microsoft Office 2013 that are built by using Microsoft Visual Studio 2010 or Microsoft Visual Studio 2012.
Note For more information about the issues that this update resolves, see the "More Information" section.
Issue 1: Unable to delete a Visual Studio Tools for Office control if another embedded object exists in the document
Assume that you have some objects embedded in a Microsoft Word document. When you try to delete a Windows Forms control in the document, you receive an error message that resembles the following:
Object is not connected to server (Exception from HRESULT: 0x800401FD (CO_E_OBJNOTCONNECTED))at Microsoft.Office.Interop.Word.OLEFormat.get_Object()at Microsoft.Office.Tools.Word.Adapter.ShapeHelpers.GetOLEFormatObject(OLEFormat oleFormat)at Microsoft.Office.Tools.Word.Adapter.DocumentControlCollectionAdapter.Microsoft.Office.Tools.Word.Contract.IDocumentControlCollectionContract.DestroyWrapper(String cookie)at Microsoft.VisualStudio.Tools.Office.Word.Internal.IDocumentControlCollectionProxy.DestroyWrapper(String cookie)at Microsoft.Office.Tools.Word.ControlCollection.InternalRemove(Int32 index, Boolean deleteContent)at Microsoft.Office.Tools.Word.ControlCollection.Remove(Object control)
Issue 2: Hostname cannot be parsed and the application may crash when you open a document from a secure UNC WebDav Share
When you try to use an SSL-based Universal Naming Convention (UNC) path in order to access a Web Distributed Authoring and Versioning (WebDAV) share, you receive an error message that resembles the following:
Invalid URI: The hostname could not be parsed.System.UriFormatException: Invalid URI: The hostname could not be parsed.at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)at System.Uri..ctor(String uriString)at Microsoft.VisualStudio.Tools.Office.Runtime.OfficeAddInDeploymentManager.OnAddInInstalling(AddInInstallingArgs args, Boolean& cancel)at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.RaiseOnAddInInstallingEvent(IClickOnceAddInInstaller addInInstaller, Uri deploymentManifestUri, AddInInstallationStatus addinSolutionState, String productName, Boolean alreadyInstalled)at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
Issue 3: Cached Data storage fails in protected documents
You cannot store data in cached data islands that are in protected documents by using a Microsoft .NET Framework 4-based application.
Issue 4: Unable to customize or check (if customized) a Microsoft Word 2010 document that uses Ink
Assume that you try to perform one of the following actions:
- You call the ServerDocument.IsCustomized function to check the customization of a Word 2010 document that uses Ink.
- You call the ServerDocument.AddCustomization function to customize a Word 2010 document that uses Ink.
In this situation, you receive an error message that resembles the following:
Office Open XML Formats document is invalid: it contains no manifest of the requested type.Source: Microsoft.VisualStudio.Tools.Applications.ServerDocument.v10.0Stack:at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.ServerAppInfo.GetPartId(Package package, PackagePart part)at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.ServerAppInfo.EnsureMaps()at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.ServerAppInfo..ctor(Package package)at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.EnsureAppInfo()at Microsoft.Office.Tools.OfficeOpenXmlAppInfoDocument.Microsoft.VisualStudio.Tools.Applications.Runtime.IAppInfoDocument.SetDocument(String fileName, Byte data, FileAccess fileAccess)at Microsoft.VisualStudio.Tools.Applications.AppInfoDocumentFactory.GetAppInfoDocument(String documentPath, Byte bytes, FileAccess access)at Microsoft.VisualStudio.Tools.Applications.ServerDocument.Initialize(Byte bytes, String documentPathOrFileType, FileAccess access, Boolean throwOnPreviousVersion)at Microsoft.VisualStudio.Tools.Applications.ServerDocument.Initialize(Byte bytes, String documentPathOrFileType, FileAccess access)at Microsoft.VisualStudio.Tools.Applications.ServerDocument..ctor(String documentPath, FileAccess access)at Microsoft.VisualStudio.Tools.Applications.ServerDocument.IsCustomized(String documentPath)
Issue 5: Add-Ins which are built with Visual Studio 2005 Tools for Office Second Edition do not work after you install build 31125 of Visual Studio Tools for Office Runtime
Assume that you install Microsoft Visual Studio 2012 or Microsoft Office 2013. Additionally, you install build 31125 of Visual Studio Tools for Office runtime for Visual Studio 2012 or Office 2013. In this situation, add-ins that are built by using Visual Studio 2005 Tools for Office Second Edition do not work.
Issue 6: Add-ins that cannot install a ClickOnce update may be disabled
After you install add-ins through a ClickOnce update, the add-ins may become disabled in a host Office application if the add-ins cannot access the update path. For example, the add-ins cannot find an update path if they try to connect to a network share that is offline, or if they try to access a file path that was moved or deleted.Note
A ClickOnce add-in will do the following if it cannot check for an update:
- Throws an exception to the user (if it is a document-level add-in) or fails silently (if it is an application-level add-in)
- Disables the add-in in the host Office application
- Removes itself from Add or Remove Programs
For issues 1-5, install the latest version of Visual Studio Tools for Office Runtime to resolve the issues.
For issue 6, install the latest version of Visual Studio Tools for Office Runtime, and then do one of the following, depending on whichever is most applicable:Case 1: The installation location of the Visual Studio Tools for Office Runtime add-in is still available
If the installation location for the Visual Studio Tools for Office Runtime add-in is still available, then rerun the Setup file on the original network share. Then, re-enable the add-in or the document-level customization in the Office application, as described in the "Re-enabling the add-in" section.Case 2: The installation location of the Visual Studio Tools for Office Runtime add-in is unavailable or different
If the installation location of the Visual Studio Tools for Office Runtime add-in is unavailable or different, then follow these steps:
- Open Registry Editor. To do this, click Start , type regeditin the Start Search box, and then press Enter.
- Locate and then click the following registry subkey:
- There are several entries that are identified by GUID. Click each entry and check the ProductName data until you find the add-in that you want to re-enable.
- After you select the add-in, double-click UpdateEnabled.
- In the Value data box, type 0, and then press OK.
Note This disables the update checking process until a new version of an add-in is explicitly installed, or until the same steps are repeated together with setting the value of UpdateEnabled to 1.
After you edit the registry, you should re-launch the Office application, and follow the steps that are described in the "Re-enabling the add-in" section.
Re-enabling the add-in
To re-enable the add-in, follow these steps:
- Open the options screen of the application (for example, you open Excel Options in Excel) and then click Add-Ins.
- Select COM Add-Ins from the Manage drop-down list.
- Click Go… to display the COM Add-Ins dialog box.
- Select the check box for the add-in that you want to re-enable, and then click OK.
How to obtain the latest version of Visual Studio Tools for Office RuntimeMicrosoft Update
This update is available from Microsoft Update
.Microsoft Download Center
The following files are available for download from the Microsoft Download Center:Download the package now.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
To apply this update rollup, you must have Visual Studio 2010 Tools for Office Runtime 4.0 installed.
You may have to restart the computer after you apply this update if the affected files are being used or locked during installation. We recommend that you exit all related application before you install the update.
The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time
item in Control Panel.x86-based versions of Visual Studio 2010 Tools for Office Runtime 4.0
x64-based versions of Visual Studio 2010 Tools for Office Runtime 4.0
|File name||File version||File size||Date||Time||Platform|
|File name||File version||File size||Date||Time||Platform|