views:

2439

answers:

10

If I launch an ASP.NET project, using Visual Studio 2008 and Internet Explorer, Visual Studio starts script debugging. I get a Script Documents node with a child node of Windows Internet Explorer and Default.aspx with a bazillion anonymous code nodes underneath.

I'm having difficulty shutting this off, other than telling VS to launch the app in FireFox. I've searched around and found the solution to shut off script debugging in Internet Explorer, but this changed nothing for me.

Has any one found a solution?

+1  A: 

Fairly certain it's an IE option and that it requires a reboot.

JRL
It is an IE option - but should not require a reboot..
markt
You might need to restart IE but not reboot the system.
David Basarab
+2  A: 

Did you check both boxes in IE to disable script debugging:

Disable Script Debugging (Internet Explorer)

Disable Script Debugging (Other)

Also, make sure that after you made the change you closed all instances of IE. Then try debugging with VS again.

Update: just tried it myself and this solution does not work.

Update2: still does not work after a reboot

Finally found a possible solution from here. Apparently this is a known issue and the workaround is to install the silverlight tools and tell the web project to debug silverlight (the debugger apparently cannot debug both silverlight and scripts).

Confirmed: The Silverlight tools solution does indeed work.

Jimmie R. Houts
That's good news. At least I'm not the only one.
Joshua Belden
Ugg, install more product to fix other product. Good find on the article though. Thank you.
Joshua Belden
Glad I could help find the answer. This is one of those really frustating issues where things don't work they way they should. Great question!
Jimmie R. Houts
worked for me too, thanks!
Matt
does anybody know if installing the SL3 or SL4 tools has the same effect?
qntmfred
ok well I just tried it with the SL3 tools and seems to work.
qntmfred
A: 

In IE, go to Internet Options -> Advanced tab, and check Disable Script Debugging ( Internet Explorer)

markt
+3  A: 

Disable all script debugging:

  • Open a new command prompt (start->run, cmd.exe). If you are on a 64-bit computer this needs to be a 32-bit prompt (start->run, c:\windows\syswow64\cmd.exe)
  • reg add HKLM\SOFTWARE\Microsoft\VisualStudio\9.0\AD7Metrics\Engine{F200A7E7-DEA5-11D0-B854-00A0244A1DE2} /v ProgramProvider /d {4FF9DEF4-8922-4D02-9379-3FFA64D1D639} /f

If you are using Visual Web Developer Express, replace 'VisualStudio' with 'VWDExpress':

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

If you want to restore your computer so that you can debug scripts again:

  • reg add HKLM\SOFTWARE\Microsoft\VisualStudio\9.0\AD7Metrics\Engine{F200A7E7-DEA5-11D0-B854-00A0244A1DE2} /v ProgramProvider /d {170EC3FC-4E80-40AB-A85A-55900C7C70DE} /f
hypoxide
I had high hopes but unfortunately, this didn't work either.
Joshua Belden
This registry tricks works well for me VSTS 2008 SP1, IE8, Win7 32Bit
Salamander2007
It only doesn't work because there is a typo in the registry key. It will work if you add a '\' between 'Engine' and '{F200A7E7-DEA5-11D0-B854-00A0244A1DE2}'.
Quick Joe Smith
A: 
Ronnie Overby
A: 

Have you tried right-clicking the file and selecting "View In Browser" to see if you get the same error? This method avoids the need to debug your code if you are certain that it is bug free of course.

Ian Roke
This is from a VS debug point of view of course.
Ian Roke
A: 
Slim
Where is the Show All Settings flag? Couldn't find anything about disabling script debugging.
Joshua Belden
Ditto: I've never seen a "Show all settings" flag. Using VS 2008 for Team Developers
Chris Lively
+1  A: 

Because this is a known problem, and a possible fix is to install Silverlight Tools, I've decided the best solution is to ditch Internet Explorer 8 and just launch my sites in FireFox.

Joshua Belden
A: 

It works for me.

This work around requires the Silverlight 2 Tools for Visual Studio 2008 SP1 to be installed. So if you don't have these tools installed, you can download them from Microsoft (http://www.microsoft.com/downloads/details.aspx?familyid=C22D6A7B-546F-4407-8EF6-D60C8EE221ED&displaylang=en). If this is not an option for you, there is some alternative work arounds at the bottom of this blog post. Right click on your project and open up project properties Go to the 'Start Options' sheet, and click the 'Silverlight' button at the bottom of the screen. Because the debugger cannot debug both Silverlight code and Script code at the same time, this will disable Script debugging and therefore avoid the problem.

http://blogs.msdn.com/greggm/archive/2009/04/06/disabling-script-debugging-in-vs-2008-ie8.aspx

A: 

Check this article.. it worked for me: http://blogs.msdn.com/greggm/archive/2009/04/06/disabling-script-debugging-in-vs-2008-ie8.aspx

Rodrigo