Ran across this the other day and thought someone else may find it useful. Javascript for the ASP.Net 2.0 controls is typically generated by a request to webresource.axd. For example when you add a menu control, you see the following in the page:
<script src="http://blogs.msdn.com/myapp/WebResource.axd?d=oTrMXXyr9lkT4MbMovPbCw2&t=632681794331014707" mce_src="http://blogs.msdn.com/myapp/WebResource.axd?d=oTrMXXyr9lkT4MbMovPbCw2&t=632681794331014707" type="text/javascript"></script>
If you browse the above URL, you get a .js file as output. If you wanted to debug this script (or other .js files) at runtime, you can use the Script Explorer included with Visual Studio 2005.
To debug inline script, you can either move the script to a .js file, use stop commands, or set a function breakpoint.
If Script Explorer is missing for you, you can use the keyboard shortcut (Ctrl+Alt+N), or add it to the IDE. Here's how to add in the Script Explorer to a toolbar or menu:
Ta det inte så hårt, jag vill bara se om vi kan få lite liv i kommentarer och diskussioner så varför
Another way (assuming script debugging is allowed in IE) is to intentionally put a javascript line in the place you want to debug that has a syntax error. The code will break there in debugging mode. You can then step over the syntax error line, the step into things and use the immediate window, etc.