M
Malik Arykov
Hello, All!
how debug embedded javascript?
how debug embedded javascript?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Alvin Bruney
The easiest way to debug script code is to just put a debug break statement
in the script code at the line you want to examine like so
[script]
stop
more script here
When the host container, usually internet explorer, executes this statement
it immediately stops on this line and allows the user the option to attach
the debugger.
Your very next step is to point the debugger to the line after the stop
statement to cause it to bypass the stop statement and then debugging
continues as normal. Remember to remove the stop statement when done.
The other options are very tedious and error prone to say the least, partly
because script only execute inside a host container and never in its own
process.
in the script code at the line you want to examine like so
[script]
stop
more script here
When the host container, usually internet explorer, executes this statement
it immediately stops on this line and allows the user the option to attach
the debugger.
Your very next step is to point the debugger to the line after the stop
statement to cause it to bypass the stop statement and then debugging
continues as normal. Remember to remove the stop statement when done.
The other options are very tedious and error prone to say the least, partly
because script only execute inside a host container and never in its own
process.
M
Malik Arykov
Hello, Anatoly!
thank's for link
thank's for link
R
Rick Spiewak
If you're working in VS.NET, you can also use the "debugger" statement, and
work directly with the VS.NET debugger.
work directly with the VS.NET debugger.
Alvin Bruney said:The easiest way to debug script code is to just put a debug break statement
in the script code at the line you want to examine like so
[script]
stop
more script here
When the host container, usually internet explorer, executes this statement
it immediately stops on this line and allows the user the option to attach
the debugger.
Your very next step is to point the debugger to the line after the stop
statement to cause it to bypass the stop statement and then debugging
continues as normal. Remember to remove the stop statement when done.
The other options are very tedious and error prone to say the least, partly
because script only execute inside a host container and never in its own
process.
--
Regards,
Alvin Bruney
Got DotNet? Get it here...
http://www.networkip.net/dotnet/tidbits/default.htm
http://devcenter.infragistics.com/Articles/ArticleTemplate.Aspx?ArticleID=2183