JavaScript Breakpoints

  • Thread starter Thread starter King Coffee
  • Start date Start date
K

King Coffee

Hi,

I set a breakpoint on line of JavaScript code within an aspx file. The debug
IDE ignores it. How can I enable JavaScript breaking ?

King
 
King said:
Hi,

I set a breakpoint on line of JavaScript code within an aspx file. The
debug IDE ignores it. How can I enable JavaScript breaking ?

King
Click to expand...

I think that only works on VS 2008 and 2008 Express editions and above,
like VS 2010.
 
I set a breakpoint on line of JavaScript code within an aspx file. The
debug IDE ignores it. How can I enable JavaScript breaking ?
Click to expand...

JavaScript breakpoints, as mentioned, are available in Visual Studio
2008+. In addition (not mentioned), you have to make sure Internet
Explorer has script debugging turned on. Open the options and go to
advanced and make sure "disable script debugging" is not clicked.

If you are not using Visual Studio 2008+, or you are attempting in a
browser other than IE, you have some issues.

For Firefox, you can debug JavaScript with an add in, like Firebug (my
personal fave). If you are not Visual Studio 2008+ and want to use IE,
you can use the Microsoft Script debugger.The Script debugger is
installed with Office XP or greater.

Peace and Grace,


--
Gregory A. Beamer (MVP)

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************
 
I'm using VS2008 Std, The set breakpoint is not a solid red circle, it has a
1/4 radius white center. I think Googles mapped JAXA is interfering with the
page code.

Thanks,
King
 
King said:
I'm using VS2008 Std, The set breakpoint is not a solid red circle, it
has a 1/4 radius white center. I think Googles mapped JAXA is
interfering with the page code.
Click to expand...

Other than JavaScript, you may want to set a breakpoint in the code
behind file to see if its going to break there. The debug icon you are
talking about indicates that breakpoints are corrupt.

Maybe, you need to attach the debugger to the ASP.Net worker process and
see if the debugger will break.
 
Have you tried adding debugger; to the script instead of a breakpoint? Not
quite the same, but you still get the Visual Studio debugger tools in your
script to help accomplish the same goals.
 
Back
Top