Comments on: Debug Javascript with IE and Visual Studio 2005

By: eoe

eoe — Mon, 25 Feb 2008 01:36:55 +0000

thx,but is many thinking to do it? I see more

By: John

John — Sun, 10 Feb 2008 11:50:19 +0000

G'day,

Thanks very much for this... most helpful!

By: SriHariT

SriHariT — Tue, 06 Nov 2007 20:05:35 +0000

ThanXXXXXXXXXXX A LOT!!!
was of great help to me in resolving extjs.com JS API issues in IE 6.
This is best debugger in absence of anything comparable to Firebug (works only with Mozilla/Firefox browser).

By: Hugo

Hugo — Wed, 01 Aug 2007 14:25:41 +0000

THX a lot!!!!! It definitively helped me solving my problem. I didn't know how to debug javascript and I'm progresivly including more of this scripts in my pages so it was a great help.....

By: Mariano Beeche

Mariano Beeche — Mon, 30 Jul 2007 16:20:55 +0000

Great thanks!

By: John Adams

John Adams — Thu, 10 May 2007 06:54:29 +0000

Very good!

By: amol mane

amol mane — Thu, 08 Mar 2007 10:04:45 +0000

good

By: David

David — Fri, 02 Feb 2007 22:42:58 +0000

--- Dennis Says: When I do this, Visual Studio barks at me saying “There is no source code available for the current location.” ---

If you start debugging javascript but use a document.write() command, everything on the page is essentially erased except for what results from your document.write() code. In this case, you WILL get the error because you have effectively erased all of the code you are trying to debug... typically you would use a getElementById() function and pair it with the innerHtml method which targets an already existing html element. This way, you can preserve the existing code and append to it rather that completely overwriting it.

By: David

David — Fri, 02 Feb 2007 22:42:39 +0000

--- Dennis Says: When I do this, Visual Studio barks at me saying “There is no source code available for the current location.” ---

If you start debugging javascript but use a document.write() command, everything on the page is essentially erased except for what results from your document.write() code. In this case, you WILL get the error because you have effectively erased all of the code you are trying to debug... typically you would use a getElementById() function and pair it with the innerHtml method which targets and already existing html element. This way, you can preserve the existing code and append to it rather that completely overwriting it.

By: brennan

brennan — Mon, 29 Jan 2007 15:59:57 +0000

You will want to use Visual Web Developer Express. And yes, it will work with a few differences than VS 2005 Pro.

MSDN Walkthrough: Debugging Web Pages in Visual Web
http://msdn2.microsoft.com/en-us/library/z9e7w6cs(VS.80).aspx