Novice tip for doing Ajax development


I spent a little time over the holiday break experimenting with Ajax development specifically with the December Atlas preview.  Overall I am very impressed with what you can do with zero client impact. 


 


One problem I ran into fairly quickly was that I needed to debug to the client side JScript I wrote.  All IE was giving me was the “error on page” icon on the bottom left and there was no obvious way to get details on what the error way. 


 


It took a little while, but I eventually found the Tools\Internet Options\Advanced\Disable Script Debugging option which is apparently checked by default.  I unchecked it and now the errors are visible when I click on the error icon in IE…


 


Hopefully this tip will save someone else sometime..


 


On to bigger and better things!

Comments (7)

  1. Leonardo Constantino says:

    Besides, you can use the full power of visual studio to debug your javascripts.

    http://weblogs.asp.net/mschwarz/archive/2005/04/19/403327.aspx

  2. Pavan Podila says:

    I would also recommend using the the VS2005 debugger for JavaScript debugging. The enhancements to the Debug Visualizers makes client-side JavaScript development all the more pleasant.

    One Up for developer productivity!

  3. Here’s a debugging tool I offer on my site, along with info on debugging Atlas and AJAX apps:

    http://www.nikhilk.net/WebDevHelperDebuggingTools.aspx

  4. Paul Dragicevich says:

    Firefox has a nice JavaScript console. It also displays any CSS errors.

  5. James Geurts says:

    There is an excellent javascript debugger for firefox: http://www.mozilla.org/projects/venkman/

  6. Gordon says:

    Brad, if you simply double-click on the IE status bar ‘error on page’ icon, the error message will be displayed in a dialog box.

Skip to main content