Re: Visual Studio only debugs javascript in .js files not .aspx fi

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Phil,

I tried to explain this to you. An ASPX page is a class that generates HTML
from the server. It is not a client-side document. It CREATES a client-side
document. The entire page code is actually a class that is executed on the
server. Therefore, when you place a breakpoint anywhere in the page code,
including any literal JavaScript in the page code, you are instructing the
debugger to break DURING THE SERVER SIDE EXECUTION OF THE PAGE. A .js file
is used by the client browser to execute JavaScript on the client side, in
the browser. It is NOT server-side executable code.

The Visual Studio JavaScript debugging tools are used to debug client-side
scripting during its execution ON THE CLIENT. Therefore, you cannot debug
JavaScript that is NOT executing during the execution of the server-side
code. At that point, it is simply text in the server-side code, and is NOT
executing.

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"Phil Johnson" <PhilJohnson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8E82E8C4-9E2E-4DCE-9197-25CD9311FD61@xxxxxxxxxxxxxxxx
Here is the thing though....

In Visual Studio (pretty expensive software)
=============================
If I put a breakpoint in a .js file... it breaks fine, the VS ide displays
where it is and I can step into it... if it makes a call to a javascript
function in an aspx page though... it gets to that line in the .js file,
steps into it... opens the correct apsx file BUT the show next statement
indicator is nowhere near the actual line it is going to run.

In Microsoft Script Editor (free software)
==========================
If I break into the Microsoft Script Editor ide displays where it is and I
can step into it... if it makes a call to a javascript function in an aspx
page though... it gets to that line in the .js file, steps into it...
opens
the correct apsx file and the show next statement indicator is on the
correct
line of code to run and you can set the next line etc

Surely the fact that Visual Studio is debugging javascript in the .js
files
means it CAN debug clientside javascript, so why does it get confused when
it
steps from a .js file into an .aspx file or even just breaks into
javascript
in an aspx file.

I must be missing something with the configuration of my tools or this is
a
pretty major issue for a web development tool.

--
Regards,

Phillip Johnson (MCSD For .NET)
PJ Software Development
www.pjsoftwaredevelopment.com


"Patrice" wrote:

For now my understanding is that you have js code embedded in server side
code so the breakpoint is applied to the server code not to the js script
the server code renders into the page...

It's likely easier to break into js client side (for example the script
debugger in IE have an option to break on the next javascript statement
that
will run). AFAIK Firebug allows to browse all javascript code and to
place
breakpoints (you also have developer toolbars for IE that could perhaps
allows this).

For IE, you also have a debugger statement that explicitely breaks into
the
debugger...

--
Patrice

"Phil Johnson" <PhilJohnson@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le
message de news: CB8D5137-CA9B-4868-BDB9-13F9696612B1@xxxxxxxxxxxxxxxx
Hi,

This is an issue that happens to me and everybody else I know and I've
never
found a way around it.

In Visual Studio (currently using 2003 but the same has happened for me
in
2005 and 2008 as well)

If I put a breakpoint in a .js file, the debugger picks it up and
breaks
into it at that point.

If I put a break in javascript in a .aspx file, the debugger kicks in,
but
the breakpoint is somewhere in the html of the aspx page and you can't
tell
where in the javascript its trying to debug.

Is there anything I can do to resolve this and debug javascript in
Visual
Studio in aspx pages, or is it a known issue we just have to live with?

Thanks.

--
Regards,

Phillip Johnson (MCSD For .NET)
PJ Software Development
www.pjsoftwaredevelopment.com





.

Relevant Pages