Thursday, 15 May 2008

Debugging in IE

When I first started using JavaScript, I used to code and debug using Firebug and then test the same on IE. Obviously sometimes this used to fail due to some porting issues and I would be left with no means to know where and why the code is failing. I am writing this article to share something which will make life easier with debugging on IE for someone who is struggling like me.

I found a world-class free debugger for IE. Visual studio is known for the best debugger out there which can directly attach to any process running on windows, but that doesn't come for free. Microsoft started giving out express editions for free, which has a debugger but that cannot attach to already running processes. Follow the steps below to make express editions help debugging our web-pages on IE.

  • Install Visual Web Developer Express which is free and can be downloaded from
    http://msdn.microsoft.com/en-us/express/aa975050.aspx

  • Enable script debug on IE - go to Tools > Internet Options > Advanced, and make sure "Disable Script Debugging (Internet Explorer)" is unchecked and "Display a notification about every script error" is checked.

  • Start a dummy project with some name.

  • Start IE in debug mode with the created dummy project - Debug->start debugging.

  • The above will start IE with debug enabled and you can open your web-page and enjoy free ultimate debugger.


 

3 comments:

Saturday Night Takeout said...

addendum: make sure IE is your defult browser, selse it'll open FF when you click on start debugging. Also, it's not possible to set breakpoints, since the code loaded isn't in the project. So yes, it's pretty good, a couple of steps over the WSH JScript debugger, but it's still not perfect yet.

PS- for inspecting the dom, I recommend either debugbar or MS developer toolbar. They're not as great as firebug, but they should do.

Saturday Night Takeout said...

Also, and this could be the most awesome advise anyone could here, please please jslint your files before debugging on IE. Keep an eye open for implied globals too, because that usually slips past the radar.

http://www.jslint.com

It might hurt your feelings, but it will save your life.

Unknown said...

Its really cooooool. I tried and failed with many other debugging tools for IE. but this looks cool and easy to use. thanks for the info.

San.