Re: aspx call stack breakpoint incorrect
- From: "ebbflow" <ebbflow@xxxxxxxxxxxxxxxxx>
- Date: Tue, 5 Jun 2007 20:07:57 -0700
I'm using vb.
An example page is below:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>test</title>
<script language=javascript>
function initialize(){
var it
it=6
}
</script>
</head>
<body onload='initialize()'>
<%response.write("hello")
%>
</body>
</html>
If I put the break point on the "it=6" it stops below that when run, and the
bracketed <%%> script is still shown. Any ideas?
Thanks
"Bryan Phillips" <bphillips@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eAb3P69pHHA.4388@xxxxxxxxxxxxxxxxxxxxxxx
Is the server side code written in C# and does it include a try/catch
block? If so, the problem is a bug in the C# compiler that generates
faulty debug symbols. (The debugger basically shows you a different
location that the actual location of the current instruction.)
--
Bryan Phillips
MCT, MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
Web Site: http://www.composablesystems.net
"ebbflow" <ebbflow@xxxxxxxxxxxxxxxxx> wrote in message
news:#d#pli6pHHA.4544@xxxxxxxxxxxxxxxxxxxx:
Hi:
I have a problem in VS 2003 that used to not exist.
I am debugging an asp.net application. In the past when I ran into a
javascript error, which originated from a javascript method call within
my
aspx page, I could use the call stack to find the point on the aspx page
where the call originated. The aspx page was fully rendered (as the user
would see it) with all of the server side script processed. Now when I
click on the call stack, I am directed to a position on the page of the
unprocessed aspx page (with server side script not processed). The point
is
indicated, but it doesn't lie on the javascript method, because it sends
me
to the unprocessed page. All other call stack debugging is working, e.g.,
when the method goes through a .js page.
Why am I no longer seeing the processed aspx page when I use the call
stack
or set a breakpoint on the javascript on an aspx page?
Thanks in advance.
.
- Follow-Ups:
- Re: aspx call stack breakpoint incorrect
- From: Bryan Phillips
- Re: aspx call stack breakpoint incorrect
- References:
- aspx call stack breakpoint incorrect
- From: ebbflow
- Re: aspx call stack breakpoint incorrect
- From: Bryan Phillips
- aspx call stack breakpoint incorrect
- Prev by Date: Re: aspx call stack breakpoint incorrect
- Next by Date: ASP.net Intellisense Not Working..... HELP!!
- Previous by thread: Re: aspx call stack breakpoint incorrect
- Next by thread: Re: aspx call stack breakpoint incorrect
- Index(es):
Relevant Pages
|