Below are some guidelines that I used to debug Ajaxjavascr ipt using ASP.NET 2.0. Based on the

method I believe that it will work with ASP.NET 2003.

First I must state that for what ever reason, my system, lack of know-how, or beta products, I could

not get the "scr ipt Explorer" to function, any typeof breakpoint to function, and except for some

immediate window sniffing of the DOM, no actual debugging on client-side scr ipt or HTML using

ASP.NET 2.0...

I could not give up, so I dug and dug. Tested and retested. Finally taking a technique that I

learned working with DCOM, VB6 and ActiveX "COM" servers, I succeeded in debugging not only the

"javascr ipt", but the "html" as well. I am able to set a breakpoint on a HTML button tag and/or

another one in the javascr ipt, then a third in my code-behind "C#" code. Using this technique I can

step "F11" thru a Ajax or scr ipt RPC call and watcheverything, well almost. Enough of the talk hereis

how. -Below are some guidelines that I used to debug Ajaxjavascr ipt using ASP.NET 2.0. Based on the

method I believe that it will work with ASP.NET 2003.

First I must state that for what ever reason, my system, lack of know-how, or beta products, I could

not get the "scr ipt Explorer" to function, any typeof breakpoint to function, and except for some

immediate window sniffing of the DOM, no actual debugging on client-side scr ipt or HTML using

ASP.NET 2.0...

I could not give up, so I dug and dug. Tested and retested. Finally taking a technique that I

learned working with DCOM, VB6 and ActiveX "COM" servers, I succeeded in debugging not only the

"javascr ipt", but the "html" as well. I am able to set a breakpoint on a HTML button tag and/or

another one in the javascr ipt, then a third in my code-behind "C#" code. Using this technique I can

step "F11" thru a Ajax or scr ipt RPC call and watcheverything, well almost. Enough of the talk　hereis

how.