Debug client-side JScript code efficiently

[Jey Run]

I read the MSDN article describing only 4 options for "Debugging
Client-Side Scripts in Your Application."
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug
/html/vxtskdebuggingclient-sidescriptsinyourapplication.asp
a.. From Microsoft Internet Explorer
a.. Using the Running Documents window
a.. In a Script
a.. In Response to an Error

But all these options are uncomfortable for everyday extensive JScript
(HTML/WSH) programming!

The only thing I need is to make some Visual Studio project with a bogus
(or real) target and be able to start Debugger with the current file
open in the IDE. The Microsoft Script Editor does this simple job very
well (it is included in Microsoft Office XP installation). But the
Microsoft Script Editor does not support projects :(

How can I get the Visual Studio (InterDev and/or .NET) debug my
client-side JScript code by just one click (F5)???

Thanks in advance...

[name]

In the end, you don't want the debugger (any debugger)
garbage your presentation.

No time, nowhere

Hell, learn javascript.

-------

Ms and javascript = not invented here.

-------------

"They" like it as much as their "inabilities".

"Jey Run" <jey...@yahoo.com> wrote in message
news:b888fv$q8v$1...@news2.netvision.net.il...

[Marc Doornik]

The best tool for DHTML/Javascript debugging is: Venkman See
http://www.hacksrus.com/~ginda/venkman/

Included in Mozilla.

[Brian Baker [MVP]]

Jey Run wrote:
> The only thing I need is to make some Visual Studio project with a bogus
> (or real) target and be able to start Debugger with the current file
> open in the IDE. The Microsoft Script Editor does this simple job very
> well (it is included in Microsoft Office XP installation). But the
> Microsoft Script Editor does not support projects :(
>
> How can I get the Visual Studio (InterDev and/or .NET) debug my
> client-side JScript code by just one click (F5)???

Can you be a little more explicit about the type of script file you want
to debug? I wasn't sure whether you were talking about JScript embedded
in an html page, JScript in a .js file that is executed by the browser, a
.js file executed by WSH, or a .wsh file.

Brian Baker
--
Microsoft MVP -- ASP / ASP.NET
Please post responses to the group

[Tim Quinn]

I have a eMatrix Web based system total converted to Mozilla even
though my client uses an IE 5.5 image. I switched to Mozilla when I
started building larger JavaScript applications. To debug deep call
stacks, you need good information such as the file the stack item came
from and it's line number. In ie, this is impossible, the stack can
only give you the function name and you don't know which file is the
source. Therefore debugging deep errors in IE takes about 5 minutes to
figure out what really happened and where the code is.

In mozilla, Exceptions have a property called stack and this is a
parsable string that contains the file name, function name and line
number in stack. The resulting stack traces are beautifull.

With good programming techniques in using open standards your Mozilla
developed pages can work in IE 5.5+. The switch is a little difficult
at first but in the end you will be on a better road.

BTW, I rarely use the venkman debugger although it has helped in some
very complex issues.

Regards,

Tim
Marc Doornik <marcd...@myrealbox.com> wrote in message news:<#6GLVLRD...@TK2MSFTNGP11.phx.gbl>...