Problem debugging embedded Client Script using IE7
We are getting an error when trying to debug client script (VBscript and JScript) from the Running Documents window using VS2003.
This only happens when the script is inline on an asp page. If there is a .js file, there is no problem.
Here is the error we get:
"The following breakpoint cannot be set:
bla bla bla
No executable code is associated with this line."
I am about to uninstall IE7 and go back to 6 because I am unable to debug our client-script-heavy applications. Any help would be appreciated.
Thanks,
Kevin
[727 byte] By [
kforrey] at [2007-12-25]
Hi Kevin,
Can you provide exact steps to reproduce the issue? Script debugging of inline script should be functioning in IE7.
Thanks
-Dave
Hi Dave,
To reproduce, do the following:
1. Create a new web solution using VS2003
2. Under Project -> Properties enable ASP debugging
3. Add an ASP file to the solution like Test.asp
4. in the asp page, add some Server script as well as some client vbs script:
5. Set test.asp as the start page and run the app
6. when the page loads go to the Running Documents window and open test.asp
7. Try to set a breakpoint in the client script.
Keep in mind this is something I did every day in IE6 and is a necessity for application support in our company. Our mission crit app is a legacy application which we are migrating as we can. It currently uses classic ASP with vb6 COM middle tier as well as asp.net using remoting to access a .net middle tier.
I am running VS2003 with sp1 and IE7 RC1.
Thanks,
Kevin
PS
I should also add that if you have an include .js file, you are able to debug as before. It seems only to be the inline script in asp pages.
Any thoughts on this problem?
Thanks,
Kevin
Had to go back to IE6......
Hi,
We're currently investigating this issue but are having problems reproducing it in IE7. Are there any more details that might help us reproduce it?
Thanks
-Dave
Hey Dave,
The only other thing worth noting is that we are using VBS and JS on the client. Any page what we have inline client code on a classic ASP page, we have the issue. If we put the client code in an include script file, then we can debug.
Thanks,
Kevin
Same problem here. IE7-RC1, Visual Studio 2003/Asp.Net 1.1
Breakpoints in script in aspx files are disabled (question mark in the red circle - The breakpoint will not currently be hit.) although the code clearly runs.
If I add the "debugger" statement in the script, it DOES break into the debugger, however it doesn't properly bind to the script context. The IDE cursor is positionned after the last line of the starting aspx page. Watch window can't resolve anything that should be in the context.
Thanks,
Wayne
Has there been any update on this issue?
Thanks,
Kevin
I meet the same problem.
When I use IE6,if I want to debug the script embeded in a aspx file which maybe include some inc files or other script files,I can use VS2003 debugger to open the runtime file and set the correct breakpoint,but in IE7,it don't work.
How can I debug embeded script in IE7?
Are we just SOL on this issue?
We're getting the same issue.
Microsoft Visual Studio 2003.
View Running Documents - we can see the document source, but breakpoints are not hit - the 'debugger' keyword no longer works either.
Disable script debugging (Internet Explorer) is unchecked.
This is occuring for 2 different developers in our shop. The only ones who have installed IE7 (RTM).
More importantly - www.hi5.com doesn't work in IE7 - wife is upset at me now for installing IE7 on her machine.
And what's up with not being able to put the menu at the top - above the address bar. And not being able to configure the address bar either - I just want to put the home page icon next to the <- -> buttons, and remove the favorite 'stars'.
One of the developers uninstalled IE7, and he was able to debug normally from within Visual Studio 2003.
The other developer was able to get debugging to work by inserting 'debugger' into the top of the page, then running the page outside of Visual Studio 2003, then when IE hit the 'debugger' keyword, it stops, asks him what he wants to do - if he says, open a new instance, then he is able to debug the script.
Uninstalling does 'fix' the problem though.
This sort of reminds me of remote debugging issues in Windows XP SP2.
why is it that i cannot open hi5 in my system
hi5 at 2007-9-3 >
