Home Dashboard Directory Help
Search

Disable script debugging in VS2012 by EJ de Wilde


Status: 

Closed


3
0
Sign in
to vote
Type: Bug
ID: 776100
Opened: 1/9/2013 12:27:04 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I have tried to disable the script debugging in VS2012 the same way as in VS201 by changing the registry setting:

reg add HKLM\SOFTWARE\Microsoft\VisualStudio\10.0\AD7Metrics\Engine\{F200A7E7-DEA5-11D0-B854-00A0244A1DE2} /v ProgramProvider /d {4FF9DEF4-8922-4D02-9379-3FFA64D1D639} /f

Changed the version to 11.0 but unfortunately this doesn't work anymore

Disabling script debugging in IE doesn't help either
Details
Sign in to post a comment.
Posted by _Greg_ on 10/16/2013 at 10:32 AM
Gregg,

Are you saying that in order to disable script debugging in Visual Studio 2012, we have to install "Silverlight 2 Tools for Visual Studio 2008 SP1", or is that taking your advice too literally. Personally I find it abhorrent that I would have to install a huge SDK that I will never use to disable a feature of Visual Studio that I will also never use.
Posted by Microsoft on 1/10/2013 at 9:14 AM
Thanks for the feedback. Visual Studio still does not have a UI exposed feature for disabling script debugging, and we are not currently planning to add one. It is still possible to disable script debugging by enabling Silverlight debugging in the same way that I described in http://blogs.msdn.com/b/greggm/archive/2009/04/06/disabling-script-debugging-in-vs-2008-ie8.aspx. I would recommend that approach if you can since that is actually tested.

The equivalent to my 'alternative work around' would be to change the 'EngineCanWatchProcess' registry value from '1' to '0' --

reg add "HKCU\Software\Microsoft\VisualStudio\11.0_Config\AD7Metrics\Engine\{F200A7E7-DEA5-11D0-B854-00A0244A1DE2}" /v EngineCanWatchProcess /t REG_DWORD /d 0 /f

Visual Studio will sometimes repopulate the HKCU keys, so you may need to redo this from time to time.

Gregg Miskelly
Visual Studio Debugger Dev

Posted by Microsoft on 1/9/2013 at 1:53 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/9/2013 at 12:50 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.