not use IE for ASP debugging

  • Thread starter Thread starter mcnewsxp
  • Start date Start date
Of course there is. In Visual Studio:

1) Select 'Processes' from the Debug menu
2) Attach the 'aspnet_wp.exe' process from the list
3) Check the 'Common Language Runtime' box
4) Close the dialog.
5) Launch your application in another browser like Firefox or Netscape

David Barkol
www.neudesic.com
 
Right click the ASPX page and choose "browse with". This will bring up a
dialog box where you can add the other browsers, and if you like set firefox
to be the default browser.

--
Thanks
Wayne Sepega
Jacksonville, Fl


"When a man sits with a pretty girl for an hour, it seems like a minute. But
let him sit on a hot stove for a minute and it's longer than any hour.
That's relativity." - Albert Einstein
 
how about this:

In Solution Explorer,
-> Right click your application, and select Properties
-> Select Configuration Properties
-> Select Debugging
-> Turn off "Always Use Internet Explorer".
Your default web browser will be used to debug your app.
 
Hi all,

I successfully got the debugger to run with Firefox (thanks to the
previous postings!), and I can set and hit breakpoints in my *.aspx.cs
files, but I see no running documents in my running documents window,
which means that I can't step through JavaScript.

Has anyone experienced this problem before and can anyone help?

thanks,
amy
 
Hi all,
I successfully got the debugger to run with Firefox (thanks to the
previous postings!), and I can set and hit breakpoints in my *.aspx.cs
files, but I see no running documents in my running documents window,
which means that I can't step through JavaScript.

Has anyone experienced this problem before and can anyone help?

thanks,
amy
Click to expand...

Place the 'debugger' keyword in your javascript code where you would
like a breakpoint. Good luck.

David Barkol
www.neudesic.com
 
Thanks--I added 'debugger' to a few places in the code, but I'm still
not getting a dump of the call stack. I've attached the debugger to
the aspnet_wp process, and I checked both the CLR and Script options.
I also attached the debugger to the firefox.exe process--is this ok?

Specifically, my problem is this--I've got one .aspx page that calls a
bunch of javascript functions, located in various files. These calls
are made when the .aspx page loads. Everything works fine in IE, but
in firefox, it looks like those javascript functions aren't being
called (I tried putting alerts in the callee functions, and those
alerts didn't execute). But when I copy & paste those JS function into
the .aspx page, they execute.

I read something here : http://www.woodger.ca/httop.htm#incl_js and
the line that caught my eye was:

When using Navigator, you cannot use Windows notation for a file
directory location (i.e. "c:\html\the_script.js"). Instead, use the
browser file notation (e.g. "file:///C|/html/the_script.js") for
Navigator (IE supports either).

I tried changing the path to the javascript files, but that didn't do
anything--I don't completely understand what "browser file notation" is
and couldn't get any useful results when I typed "browser file
notation" in Google.

For example, if my .aspx file lives in C:/Inetpub/wwwroot/AppName, and
my javascript files are in the javascript subdirectory of AppName, I
tried to put

<script language="javascript"
src="file:///./javascript/jsFile1.js"></script>

and

<script language="javascript" src="file:///C|/[full path goes
here]/jsFile1.js"></script>

None of these worked, so I'm assuming it's my fault because I don't
know what "browser file notation" is.

What really throws me off is that I created a .htm file and had it
include 2 javascript files, and tested it in both IE and firefox, and
in both browsers I could execute the Javascript code.

So what I don't understand is:
1. Am I right in thinking that for some reason, Firefox can't find my
javascript files?
2. What is "browser file notation?"
3. Why would I be able to execute the javascript from a .htm but not
from a .aspx?

thanks in advance,
Amy
 
Fixed my problems--I went into IIS and mapped *.js to MIME type
text/javascript, and now everything works fine. Thanks!

--Amy
 
Back
Top