Home Dashboard Directory Help
Search

XSLT debugging commands have been removed from visual studio 2010 by Pakua


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 776353
Opened: 1/11/2013 10:30:23 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

A month ago I had access to Debug XSLT under the xml menu in visual studio 2010. When I attempted to debug today the command was missing. I then attempted to customize the menu and add the commands back, but the commands are not listed under the xml item. I still have the commands available for vs 2008 and 2005 and i know that xslt profiler was included with vs 2010.

I have found what has caused the issue. Every person in my department that has installed the most recient windows updates no longer can use the xslt debuggin options. This appears to be a bug with this update.

Update for Microsoft Visual Studio 2010 Tools for Office Runtime (KB2796590)

Installation date: ‎1/‎9/‎2013 10:03 AM

Installation status: Successful

Update type: Important

Fixes for the following issues found in Visual Studio Tools for Office Runtime in Visual Studio 2010: Unable to delete VSTO Control if another embedded object exists in the document; Hostname cannot be parsed (and crash) when opening a document from secure UNC WebDav Share; Cached Data storage fails in protected documents; Cannot customize, or check if customized, any Word 2010 document with Ink; Adds runtime support for addins that target .NET 4.5


Details
Sign in to post a comment.
Posted by Pakua on 1/14/2013 at 10:27 AM
Please send this bug to the appropriate support team then.
Posted by Microsoft on 1/13/2013 at 10:24 PM
Thanks for your feedback . The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
<http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx>
Posted by Microsoft on 1/11/2013 at 10:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.